Dynamics 365 Project Operations: Diagnosing an empty staging table and integration journal
Tested on:
Project Operations solution version 4.9.0.52 (pre-alpha), F&O 10.0.16.
I recently redeployed my F&O T2 and Dataverse environments in hopes of seeing my F&O T2 appear in PPAC. While the whole deployment process has small details that have changed and evolved since ProjOps’ GA, the overall process has remained the same: Deploy F&O, deploy Dataverse, link environments, choose legal…
Continue Reading Antti Pajunen’s Article on their blog
Dynamics 365 Project Operations: Diagnosing an empty staging table and integration journal
Tested on:Project Operations solution version 4.9.0.52 (pre-alpha), F&O 10.0.16. I recently redeployed my F&O T2 and Dataverse environments in hopes of seeing my F&O T2 appear in PPAC. While the whole deployment process has small details that have changed and evolved since ProjOps’ GA, the overall process has remained the same: Deploy F&O, deploy Dataverse, link environments, choose legal entities, apply Dual Write maps, run Dual Write maps.
Blog Syndicated with Antti Pajunen’s Permission
More About This Author
Array
Dyn365CE2023.02.10Using environment variables in a flow’s Excel action- Dyn365CE2023.01.22Dynamics 365 Project Operations: Approving time entries using the Project Approver Admin role
- Dyn365CE2022.12.27Time-zone agnostic price defaulting in Project Operations
- Dyn365CE2022.12.05External scheduling in Project Operations
