20

Request to Reference Non-Primary Information from Primary Audit Logs


There are customer records A and A’, with A being the primary. When merging, only the information from A is adopted, and no integration event is recorded in A’s audit history. If the merge itself was an error or if you want to check A’s information, you will need to search for the inactive customer information, which becomes difficult over time. Without a merge log on the primary side, there is a risk of not realizing that an incorrect merge has occurred.


Therefore, We propose that a merge log be recorded on the primary side as well, allowing reference to the non-primary data.

Category: Dataverse
STATUS DETAILS
New