Provision a new environment
Applies To: Project Operations for resource/non-stocked based scenarios
Note
Effective November 2020:
- Common Data Service has been renamed to Microsoft Dataverse. For more information, see Power Automate Blog.
- Some terminology in Microsoft Dataverse has been updated. For example, entity is now table and field is now column. For more information, see Terminology updates.
This topic will be updated soon to reflect the latest terminology.
This topic provides information about how to provision a new Dynamics 365 Project Operations environment for resource/non-stocked based scenarios.
Enable Project Operations automated provisioning in an LCS project
Use following steps to enable the Project Operations automated provisioning flow for your LCS project.
- Go to LCS and select the Preview Feature management tile.
- In the Preview feature list, select Project Operations Feature, and then select Preview feature enabled to enable Project Operations.
Note
This step is performed only one time per LCS project.
Provision a Project Operations environment
- Open a new Dynamics 365 Finance demo environment or sandbox/ production environment deployment.
- Walk through the Environment provisioning wizard.
Important
Make sure selected application version is 10.0.13 or higher.
- To provision Project Operations, under Advance settings, select Common Data Service.
- Enable the Common Data Service Setting by selecting Yes and then enter information in the required fields:
- Name
- Region
- Language
- Currency
In the Common Data Service Template field, select Project Operations
Select the environment type for your deployment. A subscription-based trial will let you deploy a CDS environment for 30 days.
Important
Select Agree to acknowledge the terms of service and then select Done to return to the deployment settings.
Optional - Apply demo data to the environment. Go to Advanced settings, select Customize SQL Database Configuration, and set Specify a dataset for Application database to Demo.
Complete the remaining required fields in the wizard and confirm the deployment. The time to provision the environment varies based on the environment type. Provisioning might take up to six hours.
After the deployment completes successfully, the environment will show as Deployed.
- To confirm that the environment has deployed successfully, select Login and log on to the environment to confirm.
Apply updates to the Finance environment
Project Operations requires a Finance environment with application version 10.0.13 (10.0.569.20009) or higher.
You might need to apply quality updates to your Finance environment to receive this version.
- In LCS, on the Environment details page, in the Available Updates section, select View Update.
- On the Binary updates page, select Save package.
- Click Select all and then select Save package.
- Enter a name and a description of the package, and then select Save. Depending on the internet connection, this process might take some time.
- After the package is saved, select Done and save this package to the Assets library in your LCS project.
Saving and validating the package might take ~15 minutes.
- To apply the update, navigate to the Environment details page in LCS and select Maintain > Apply updates.
- In the updates list select the package you created, and select Apply.
Environment servicing will take some time. After it is complete, the environment will return to a deployed state.
Establish a Dual Write connection
- In your LCS project, go to the Environment details page.
- Under Common Data Service Environment Information, select Link to CDS for Apps.
- After the link is complete, select Link to CDS for Apps again. You will be redirected to Dual Write in Finance.
- Select Apply Solution to access the entities that will be mapped in the integration.
- Select both solutions, Dynamics 365 Finance and Operations Dual Write Entity Map and Dynamics 365 Project Operations Dual Write Entity Maps, and then select Apply.
After the solutions are applied, the Dual Write entities are applied to the environment.
After the entities are applied, all available mappings are listed in the environment.
Refresh the data entities after the update
- In Finance, go to the Data management workspace.
- Select the Framework parameters tile.
- On the Entity settings page, select Refresh Entity list.
The refresh is going to take approximately 20 minutes. You will receive an alert when it is complete.
Update security settings on Project Operations on Dataverse
Go to Project Operations on your Dataverse environment.
Go to Settings > Security > Security roles.
On the Security roles page, in the list of roles, select dual-write app user and select the Custom Entities tab.
Verify that the role has Read and Append To permissions for the:
- Currency Exchange Rate Type
- Chart Of Accounts
- Fiscal Calendar
- Ledger
After the security role is updated, go to Settings > Security > Teams, and select the default team in the Local Business Owner team view.
Select Manage Roles and verify that the dual-write app user security privilege is applied to this team.
Run Project Operations Dual Write maps
- In your LCS project, go to the Environment details page.
- Under Common Data Service Environment Information, select Link to CDS for Apps. After you select the link, you will be redirected to the list of entities in the mappings.
- Start the maps as described in the following table. Make sure to follow the sequence as listed.
| Entity Map | Refresh entity | Initial sync | Master for initial sync | Run prerequisites | Prerequisites initial sync |
|---|---|---|---|---|---|
| Project Resource Roles for All Companies (bookableresourcecategories) | No | Yes | Common Data Service | No | N\A |
| Legal entities (cdm_companies) | No | Yes | Finance and Operations apps | No | N\A |
| Ledger (msdyn_ledgers) | No | Yes | Finance and Operations apps | Yes | Yes, Finance and Operations apps |
| Project Operations integration actuals (msdyn_actuals) | No | No | N\A | Yes | No |
| Project contract lines (salesorderdetails) | No | No | N\A | No | No |
| Integration entity for project transaction relationships (msdyn_transactionconnections) | No | No | N\A | No | N\A |
| Project Operations integration contract line milestones (msdyn_contractlinesscheduleofvalues) | No | No | N\A | No | N\A |
| Project Operations integration entity for expense estimates (msdyn_estimateslines) | No | No | N\A | No | N\A |
| Project Operations integration project expense categories export entity (msdyn_expensecategories) | No | No | N\A | No | N\A |
| Project Operations integration project expenses export entity (msdyn_expenses) | Yes | No | N\A | No | N\A |
| Project Operations integration entity for hour estimates (msdyn_resourceassignments) | Yes | No | N\A | No | N\A |
- To refresh the entity, select the map name, and then select Refresh entities.
- After the refresh is complete, run the map. Before you enable the next map, verify that the map in the table is in a state of Running. Running maps with a larger number of prerequisites might take some time.
To run a map with prerequisites, enable the Show related entity maps toggle. If the table indicates Prerequisite initial sync is No, verify that the Initial sync flag is Off in all the prerequisite maps before you run it.
- Validate all project related maps are in the running state.
Apply configuration data in CDS for Project Operations (optional)
If you have applied demo data to the Finance environment, see Set up and apply configuration data in the Common Data Service for Project Operations to apply demo data to CDS environment.
Your Project Operations environment is now provisioned and configured.
Note
Can you tell us about your documentation language preferences? Take a short survey.
The survey will take about seven minutes. No personal data is collected (privacy statement).