Views:

Applies to Product -Dynamics 365 Supply Chain Management


What’s happening?
The customer is concerned about whether the LCS Environment Move Database operation from production will replace existing dual write mappings and affect the current dual write process between Dynamics 365 Finance and Operations (F&O) and Dynamics CRM, as well as any running Power Apps.


Reason:
The refresh database operation will remove the existing dual-write configuration. After the refresh, the environments must be relinked, and the dual-write mappings need to be reactivated manually.


Resolution:

  1. Backup the Current Environment: Before performing the refresh, create a backup of the current environment by generating a database .bacpac file.
  2. Restore from Production: Follow the steps to restore the environment from the Production database.
  3. Reconfigure Dual Write: After the refresh, set up a new link on the target environment. The dual-write mappings must be reactivated manually.
  4. Clean Up Specific Tables: After the data refresh, clean up the following tables:
  5. Finance and Operations apps tables:
    • DualWriteProjectConfiguration
    • DualWriteProjectFieldConfiguration
    • BusinessEventsDefinition
  6. Dataverse tables:
    • DualwriteRuntimeConfiguration
  7. Refer to Documentation: For more details on the dual-write impact after a database refresh, refer to the official documentation: Dual Write FAQ.
If further assistance is needed, please reach out to support.