Power Apps Entities to OnePlan Plans – Support

This article explains how to set up the integration between Power Apps entities and OnePlan plans.

Before beginning, the following assumptions are made in order for this integration setup to be successful:

Office 365 is up and running
A Power Apps or Dynamics environment is up and running
OnePlan group is set up in the same Office365 tenant

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.

Log in to your OnePlan group with your Office365 account.
Open the Admin pages by clicking on the Settings gear.
Select Integration in the admin navigation.
Click the + (plus) icon in the Authentication Keys section.
Save the key name and 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

Go to https://my.oneconnect.ai
Configure the following integration: Power Apps Entities to OnePlan. Click the Configure button. The integration configuration form will open.

Power Apps Section

Authorization: Click on the Authorize button to approve consent to use the default Power Apps app registration. Review the app authorization information in the popup, and click Accept.

Note

See How to approve consent for more information.
Client Id (Azure App Id): Only use this field if you are not using the default Power Apps app registration for this integration. Enter your App Id. See Step 8: Complete the PowerApps setup actions for instructions on how to create and collect your own Application Registration Id.
Power Apps Url: Enter the URL of the Power Apps environment you are connecting to.
Username: Enter your Power Apps username. Account needs a Power Apps license, System Admin and System Customizer permissions in the Power Apps environment you are connecting to.
Password: Enter your Power Apps password.
Additional Options: Enter the entity name to be synchronized ("oneplan_project" entity for adaptive PPM).
Click Test. If the connection test is successful (you will see a notification), click Next.

OnePlan Section

OnePlan Group Name: Enter the name of the OnePlan group that you are connecting to.
Authentication Key: Enter/paste the OnePlan Key that you saved from the earlier OnePlan Setup steps.
Integration Key Name: Leave blank.
(Optional) OnePlan URL: For clients that have their oneplan.ai hosted outside of the United States, please enter the OnePlan URL used.

Note

Options currently are: https://au.oneplan.ai, https://ca.oneplan.ai, https://eu.oneplan.ai.
Click Test. If the connection test is successful (you will see a notification), click Next.

Filter and 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.

Integration Information

Functionality

This integration has two main use cases for functionality.

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

Scheduled Jobs

The following scheduled jobs are installed by default.

SynchLookups
- Synchronize any mapped lookup/options set fields’ choices from Dynamics into OnePlan
OnePlanUpdate
- Synchronize projects and tasks from Project for the Web to OnePlan
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