Editar

Compartir a través de

Unlink and relink dual-write environments

  • Artículo

When you unlink and relink Dual-write connection between environments, you need to delete the data from the key tables. This requirement applies to sandbox, production, and user acceptance test (UAT) environments during activities like backup and restore. This article describes how to reset the connection, and how to delete the data in the key tables.

Scenario: Reset linking

If you want to reset your existing sandbox Dataverse instance that is linked for Dual-write or you want to change the linking to the Dataverse instance currently targeted in Lifecycle Services, follow these steps:

Note

If you receive a message in Lifecycle Services that states "Microsoft has detected that your environment is linked via Dual-write to a different Power Platform environment" the following steps will help you resolve the issue when a previous link has been established.

  1. Sign in to the finance and operations app.
  2. Navigate to Data management > Dual-write.
  3. Stop all entity maps.
  4. Ensure the environment targeted via Lifecycle Services is properly configured. For more information, see System requirements and prerequisites.
  5. To reset all Dual-write connections and configurations, select Reset. For more information about the reset process, see Reset dual-write connections.

Scenario: Back up and restore

When you back up and restore an environment, you may see unexpected data movement or errors. These errors happen if a previous Dual-write connection was established with the backup/restore environment and table maps weren't stopped. This causes data in key tables not to be cleared.

To mitigate this issue, follow these steps.

  1. Sign in to the targeted Finance and Operations app.

  2. Delete the data from the following tables:

    • DualWriteProjectConfiguration
    • DualWriteProjectFieldConfiguration
    • BusinessEventsDefinition

  3. Sign in to the targeted Dataverse environment.

  4. Delete the data from the Dual Write Runtime Configurations table.

  5. To re-establish applicable connections, reset the connection as detailed in the "Reset linking" section.

Known issues

SecureConfig Organization error

When you try to copy, update, or delete records after copying the environment, the following error appears: SecureConfig Organization (ProjOpsTest4) does not match actual CRM Organization (org6459f7a8_195867911_20200717T174709).

To mitigate the error, follow these steps.

  1. In the customer engagement app, select Advanced find.
  2. In the Look for field, select Dual Write Runtime Configurations.
  3. Select Results.
  4. Rows are displayed. Select all the rows.
  5. Select the Delete icon.