Dual-write – Environments and ALM
In a previous post, I gave an introduction to dual-write, the OOB infrastructure for setting up integration between Dynamics 365 Finance and Operations (F&O) an
In the previous post, an introduction to dual-write, the OOB infrastructure setting up integration between Dynamics 365 Finance and Operations (F&O) and Dataverse/ Dynamics 365 CE apps was discussed. This post will further unveil the dual-write topic focusing on environments. It's of importance to note, the management of F&O environments is shifting from LCS to PPAC (Power Platform Admin Center). The setup method of these environments is about to change. The environmental findings will be discussed as per the 'old way' structure of F&O setup in LCS.
- Starting with a list of findings, they will be delved into one by one.
- Environment strategy is a key aspect in managing F&O environments.
- For a POC, having one set of F&O Dataverse is good enough.
- For anything more than a POC, it will require a deep dive analysis.
Detailed look on the main topic
The transition from LCS to PPAC for managing F&O environments is a significant development. With this, the provisioning of environments will drastically change. While one F&O set within Dataverse suffices for a POC, tackling projects beyond a POC will require a more robust and nuanced approach. The environmental findings, formulated based on the LCS structure of F&O, provide key insights during such scenarios. Understanding and employing the right environmental strategy becomes instrumental in successful F&O operations and interactions with Dataverse/ Dynamics 365 CE apps.
Read the full article Dual-write – Environments and ALM
Learn about Dual-write – Environments and ALM
Dual-write is a way to integrate Dynamics 365 Finance and Operations (F&O) and Dataverse/ Dynamics 365 CE apps. This post will discuss some general findings related to dual-write environments, based on the setup with F&O in LCS. The findings include that one set of F&O and Dataverse is good for a POC, but more than one set may be needed for a production environment; that F&O and Dataverse environments must be kept in sync for dual-write to work properly; that F&O and Dataverse must be in the same region to work properly; that F&O and Dataverse environments must have the same name; that F&O and Dataverse environments must have the same currency; that dual-write can be used with on-premise F&O environments; and that the integration must be tested thoroughly before being put into production.
More links on about Dual-write – Environments and ALM
- Application lifecycle management - Finance & Operations
- Aug 11, 2022 — By making dual-write solution-aware, you enable basic application lifecycle management (ALM) capabilities, such as transportation and ...
- Dual-write table mappings: copy to other environments
- Jul 27, 2021 — Learn how to move Dual-write table mappings between Dataverse and Dynamics 365 Finance and Operations environments.
- Dual-write - Power Wiki
- Nov 8, 2022 — Dual-write is an out-of-box infrastructure which can be setup to provide "near-real-time" integration between Dataverse/Dynamics 365 CE apps ...
- Kurt Hatlevik – Dynamics 365 Blog | Dynamics 365
- Dual Write : Sync on-demand with the Supply Chain Management pricing engine ... What is the ALM process and environments, release process, CI/CD, ...
- How to design data entity for dual-write in Dynamics 365 FO
- Oct 1, 2022 — Design data entity for dual-write in Dynamics 365 Finance & Operations. ... simplify & better control ALM, CE & ERP-related business ...
- United at last: Dynamics 365 Dual-write goes GA
- Mar 29, 2020 — Dual-write isn't your everyday CRM-ERP integration, though. It is a near real-time synchronization of data between the Finance and Operations ...
Keywords
Microsoft Dynamics, Dynamics 365, Power Platform Admin Center, LCS, Dataverse, F&O, Dual-Write, ALM, Environment Strategy