Installation and setup of dual-write
The process of installing and setting up dual-write can vary, depending on the scenario and starting point for your individual implementation. For the sake of consistency, assume that you meet all prerequisites of the finance and operations apps environment and that the Dataverse environments are complete. Also, assume that each environment is available, working, and ready to be linked.
For more information, see Guidance for dual-write setup.
If you're deploying a new finance and operations apps environment and a new Dataverse environment, you can use deployment of an integrated environment. This deployment allows you to set up dual-write directly from Microsoft Dynamics 365 Lifecycle Services, which would be a seamless experience for your customers.
For more information, see Enable Power Platform integration.
If you have an existing finance and operations apps environment and an existing Dataverse environment with a database, you should first set up the linking through the finance and operations apps environment. Go to the Data management workspace and select the Dual-write tile to begin the process of linking.
When you select the button to create a new link to an environment, a connection wizard starts and directs you through the necessary setup. Select an existing Dataverse environment that you want to link to. Select the legal entities that you want to connect to the Dataverse environment, and then turn on dual-write for the data therein.
The next step is to validate that all requirements of the health check are complete. If they aren't complete, you might need to do extra setup steps and determine which prerequisites are missing. To determine those prerequisites and steps, see Guidance for dual-write setup.
After all health checks have passed, you can continue through the wizard and create the link between the finance and operations apps environment and the Dataverse environment. After you create the link, you can import or apply solutions to create, import, and select table mappings for the entities that pass data between the environments. Some table mappings might require that you run extra mappings simultaneously. These required extra mappings display when you try to start the mappings.
Each mapping that you turn on also has an option for initial synchronization. For initial synchronization, make sure that you consider single-threaded tables or multi-threaded tables, constraints for the data migrations, and limits of rows. For single-threaded tables, such as accounts, vendors, and tax codes, we generally recommend that you first migrate the data into finance and operations apps. Then, the system triggers the initial sync to move the data over to Dataverse. For multi-threaded tables, you need to first migrate data into Dataverse and then trigger the initial sync to move the data over to finance and operations apps.
For more information, see Considerations for initial synchronization.
Table mappings have several different statuses because you turn on the mappings after you link them. When you turn on a table map for dual-write, it begins at the Not running status. Then, the table map goes through an initialization phase, where it does an initial write by copying the pre-existing data on tables on both sides of the link. Finally, when the table mapping is activated, the table map sets the status to Running. From the run state, you can stop or pause the mapping. When you pause a mapping, the system queues all changes until you resume it. When you resume the mapping, the table goes into catch-up mode, where the system plays back all queued changes to help ensure that the table is up to date.
For more information, see the Example: Enabling the Customers V3-Contacts table map section of Enable table maps for dual-write.