We should be able to have 2 separate "Table Mappings" pointing to the same Source/Target entities of F&O and CE. If we create a "Table Mapping" for a Source/Target combination that already exists, Dual Write will create a new version.

We need this f.e. for our "Prospects"-integration at a customer:

• F&O Prospects are created with a “100....”-number and they must be created in CE and update specific information in CE. CE will send back some information like the “CE Unique Identifier” of the “Prospect” and other important information.
• CE Prospects are created with a “50….”-number and they must be created in F&O and update specific information in F&O. F&O will send back some information like the “REC ID” and other important information.

If we use no filters it will update some fields that shouldn't be updated in F&O or in CE.

If we use filters, then it will not send some critical information back to F&O or CE.

Creating a "Custom Entity" is not a solution, as it will not get all the updates Microsoft is pushing to their entities. Also Microsoft will not give any support on "Custom Entities".

We had the same kind of question at multiple customers. This was possible using some other 3rd party tools and we need to convince them to use the OOB Dual Write.