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
#Dyn365CE2021.04.07Dynamics 365 Project Operations: Diagnosing an empty staging table and integration journal- #Dyn365CE2021.04.01Project for the web: Deploying to sandbox and production Dataverse environments and syncing users
- #Dyn365CE2021.02.11Two-way sync of bookings between Dynamics 365 and Outlook, Part I – Change Notifications
- #Dyn365CE2021.01.13Dynamics 365 Project Operations: Changing the “bill to” customer after invoicing
