Microsoft Dynamics 365 | Integration, Dataverse...

Dual-write | Adding Additional Mappings to Existing Tables

(2) Share

Report

Posted on by LC-13061756-0

Hello all,

I would like to add an additional mapping for existing mapped tables in Dual-write, so that the same two tables can be mapped based on different fields, depending on a specific condition.

However, when we use the "Add table map" button in the Dual-write configuration and select tables that already have an existing mapping, the system creates a new version of the existing mapping instead of adding a separate mapping (Image 1).

Upon reviewing standard solutions, I have noticed that some tables are indeed mapped based on different criteria. One such example is the CSD Contacts V2, as shown in images below.

Does anyone have insights on how we can achieve a similar setup to the CDS Contacts V2 table for other tables?

Thank you in advance!

Categories:

Power Platform integration

I have the same question (2)

All responses (4)

Answers (0)

Komi Siabi 13,208 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The behavior you get, when you edit an exiting map is normal. You must "save as" a new version.

I am not so certain about the second concern you raised. Can you clearify?

``Upon reviewing standard solutions, I have noticed that some tables are indeed mapped based on different criteria. One such example is the CSD Contacts V2, as shown in images below.``

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi there 👋

Thanks for your detailed question!

You're absolutely right—Dual-write typically creates a new version of an existing mapping when you try to add a mapping for the same table pair. However, as you've observed with CDS Contacts V2, it is possible to configure multiple mappings for the same tables using query filters and custom logic.

✅ Here’s how you can approach this:

Use query filters in the mapping configuration (as shown in your example with AssociationContactType = 1) to differentiate records based on conditions.

Create separate table map entries with distinct filters and logic, even if they point to the same source and target tables.

Ensure that each mapping has a unique purpose and filter criteria, and that they don’t conflict or overlap in data sync.

You may need to customize the data project or use custom entities if the standard mapping behavior doesn’t meet your needs.

💡 This setup allows you to simulate multiple mappings for the same tables—each handling a different subset of data based on business rules.

Hope this helps!
✅ Please mark this reply as helpful if it answered your question.
Best regards! 👋

Was this reply helpful? Yes No
MB-28041419-0 4 on at

Like (0)

Report
Copy link

Link copied!

Hi @LC-13061756-0
I'm facing exact same challenge and actually wanted to make an exact same post 😊 Did you find a solution? I was trying with adding versions with filters and different conditions on mappings, but no luck - I'm always ending up with one mapping version available for running. It's especially surprising considering the out-of-the-box solutions (like 4 Contacts entity maps).

With regards,
Mac

Was this reply helpful? Yes No
Suggested answer

MB-28041419-0 4 on at

Like (0)

Report
Copy link

Link copied!
Update to the case - here's how to make it work:

Create a new solution in make.powerapps.com that's connected to your F&O.

Add there an existing dual-write map (it's under the "Other" list).

Add the map that you'd like to have duplicated.

Publish the solution.

Go back to F&O Dual-Write settings, go to "apply solution" - your newly created solution should be there on the list.

Apply the solution and you'll find the new mapping.

Was this reply helpful? Yes No