Dataverse - Data full restore only

(1) Share

Report

Posted on by Woody

Currently our Dataverse environment is linked to D365 F&O for dual write use when the F&O team restores data from Production to UAT it brakes the link cause F&O UAT data now matches Production F&O data but Dataverse still has UAT data.

I would like to know if anybody knows of a way to do a Data only restore from Prod Dataverse to UAT Dataverse with out the risk of loosing development on Dataverse UAT environment.

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 3,323 on at

Like
a
(0)

Report
Copy link

Link copied!
Yes—you can refresh UAT data without losing development, but not by using a full Dataverse restore. You need a data-only refresh strategy, not environment restore.

Why your issue happens

With Dual Write between Microsoft Dataverse and Dynamics 365 Finance and Operations:

F&O UAT is refreshed from Prod

Dataverse UAT still has old UAT data

Result:

Data mismatch → Dual Write breaks

Recommended approaches (safe options)
Option 1: Configuration Migration Tool (BEST)

Use:

Configuration Migration Tool

What it does:

Moves data only

Keeps:

Schema

Customizations

Steps:

Export data from Prod Dataverse

Import into UAT Dataverse

Select only required entities

Safe for development environments

Option 2: Dataflows / Power Query

Use:

Dataflows in Dataverse

Benefits:

Incremental load

Controlled refresh

Good for ongoing sync scenarios

Option 3: Power Automate / ETL sync

Use:

Microsoft Power Automate

Pattern:

Read from Prod

Write to UAT

Flexible but slower for large datasets

Was this reply helpful? Yes No
Bala Nira 6 on at

Like
a
(0)

Report
Copy link

Link copied!
Before any refresh — export your UAT Dataverse solutions first. After the restore, reimport them. That's your safety net for dev work.For the refresh itself, always do both sides at the same Point-In-Time:

Stop dual-write table maps in UAT

F&O team restores Prod → UAT

You restore Dataverse Prod → UAT (same timestamp)

Reset the dual-write link in F&O UAT

Apply Solutions → restart maps → Initial Sync

This keeps both sides aligned and avoids the broken link entirely.

Long term — if this keeps happening, push for a dedicated PRE-UAT environment pair that never gets refreshed. Use that for Dataverse dev/testing, and let UAT be the environment that gets the regular Prod refresh. Saves a lot of pain.

Was this reply helpful? Yes No