OneConnect

OnePlan and Project for the Web

Updated on

This article explains how to set up the integration between your OnePlan group/environment and Microsoft Project for the Web.

How to Use OnePlan with Project for the Web

Want to see the integration in use to understand how it works before setting it up?  Watch the following video that highlights OnePlan with Project for the Web.

The use case for this integration is the plan gets created in OnePlan FIRST. Then, from OnePlan, create a synced/mapped project in Project for the Web. The projects are not to be created manually in Project for the Web.  

OnePlan Setup

In order to do the OnePlan setup, you need to be an admin, meaning you are a user with Owner permissions in OnePlan.

 

  1. Log in to your OnePlan group with your Office365 account.
  2. Open the Admin pages by clicking on the Settings gear.
  3. Select Integration in the admin navigation.  
  4. Click the + (plus) icon in the Authentication Keys section.
  5. Save the key name & generated key somewhere (such as in a notepad doc), as once you navigate away, the key cannot be seen.  To be used at a later step in the OneConnect configuration.

OneConnect Setup

  1. Go to https://my.oneconnect.ai
  2. Configure the following integration: OnePlan and Project for the Web.  Click the Configure button.

ONEPLAN

  1. Authentication Key: Enter/paste the OnePlan Key that you saved from the earlier OnePlan Setup steps.
  2. Click the Next button.

INTEGRATOR

  1. Click the Next button.

PROJECT FOR THE WEB

  1. Project for the Web URL: Enter in the CDS/Dynamics URL (eq. https://org123.crm.dynamics.com/).
  2. Enter in username and password that will be used (Preferably a service account).
    NOTE: The user needs to have admin access to the PowerApps environment you are connecting to.
  3. Client ID (Azure App ID):
    • If you are a tenant admin: Click Click here to approve consent to use the default app registration for this tenant.
    • Otherwise: Follow CDS (Common Data Service) / Dynamics Setup. Then enter/paste the Application (Client) ID from CDS/Dynamics that you saved from the CDS/Dynamics Setup steps.
  4. Click Save.

Filter & Field Mapping

A filter must be added to the OneConnect filters,  to distinguish which projects in Project for the Web are to synchronize with OnePlan.  Add a filter for only Projects that don't have a blank ID, in other words, don't include projects that don't have a mapped OnePlan plan.   The ID fields referenced in the filter must also be mapped in the field mappings section. 

CDS (Common Data Service) / Dynamics Setup

In order to do the CDS (Common Data Service)/Dynamics setup, you need to have an admin account.

NOTE: The service account used for integration must have the ‘System administrator’ or ‘System Customizer’ role in Dynamics 365.

  1. Go to https://portal.azure.com.  An Admin account required to approve API access.
  2. On the top left corner, expand the portal menu navigation and select “Azure Active Directory
  3. On the left navigation, select “App Registrations
  4. Click “New Registration
    • Name: Fill out whatever name to identify the App Registration.
    • Click the Register button.

Once “Registered”, you will be directed to the recently created App configuration home page

Save the “Application (client) ID” – To be used at a later step in the OneConnect configuration.

 

Go to the “Authentication” tab on the left (located on the left under “Manage” section)

Make sure on the “Supported account types” section, “Accounts in this organizational directory only” is selected. Also make sure to enable the "Allow Public Client Flows" from the "Advanced Settings" section by toggling it to Yes.

Go to the “API Permissions” tab on the left (located on the left under “Manage” section)

Click on “Add a permission

  1. Add “Dynamics CRM
    • Select “Delegated permissions
    • Check the “user_impersonation” permission
    • Then finally “Add permissions

Make sure that an Admin account can grant the admin consent for the API permission. Once it is granted, the API permissions should look like the following screenshot below.

Integration Information

Functionality

This integration has two main use cases for functionality.

  1. Create or Update plans from OnePlan as a Project in Project for the Web
  2. Create or Update tasks from Project for the Web into OnePlan schedule

Scheduled Jobs

The following scheduled jobs are installed by default.  

  1. SynchLookups
    • Synchronize any mapped lookup/options set fields’ choices from Dynamics into OnePlan
  2. OnePlanUpdate
    • Synchronize projects and tasks from Project for the Web to OnePlan
  3. OnePlanPublish
    • Synchronize OnePlan plans into Project for the Web as projects

Default Field Mappings

Plans (OnePlan) <--> Projects (Project for the Web)

OnePlan Fields

Project for the Web Fields

Direction

Name

Name

Both

Effort

Effort

Both

Tasks (OnePlan) <--> Tasks (Project for the Web)

OnePlan Fields

Project for the Web Fields

Direction

Name

Project Task Name

Both

Effort

Effort

Both

Assigned To

Assigned to

Both

Previous Article What is a Relay?
Next Article OnePlan & Tabular Data for Bulk Resource Import