Override is possible only for manual merges. Please go through this documentation:
Otherwise, the merge survivorship happens as per these rules explained in this documentation:
Doesn't seems we have any such configuration which could help you to achieve this use case directly. You have to Write custom code to achieve this use case.
In MDM generally the surviorship happens either of 2 levels
1. Row level survivorship - If no columns enabled for Trust, then the Light trust framework elevates the entire row that is with recent most Last_update_date
2. Cell level survivorship - When Trust enabled on a column, the Trust and survivorship happens based on the curve defined
But in both cases we have no control over the Rowid value that survives. It could be lowest or highest Rowid value based on consolidation_ind and other factors.
If the user-defined column that you want to control the survivorship is a unique id type, then try our Persistent ID module where you can configure based on below data points
Not Null. Value is 0 or 1.
Set to 0 for oldest XREF survivorship, by create date and lowest ROWID_XREF.
Set to 1 for Target ROWID_OBJECT. The winning Persistent ID value is the XREF record where the ROWID_OBJECT equals ORIG_ROWID_OBJECT.Note: For value of 1, both IGNORE_XREF_HSI and IGNORE_XREF_TIMELINE are not used, and both are ignored
Thanks Sathiesh for your response.
The user defined column which we want to survive is not a unique id . But we need to get the user defined column's value of winning Rowid object just before merge overrides the value.
Can we use HIST table to get this value ?
Your help is highly appreciated!
I believe what you need is your Col X value should stay same for a Rowid from beginning to End.
Which is technically the BO record should hold the XREF value of Col X where BO.ROWID_OBJECT=XREF.ORIG_ROWID_OBJECT.
You can perform this update from XREF to BO in the PostMerge UE.
Can you please clarify if you are not looking for an older value to survive after the initial merge i.e. after 2 records are merged and the first value that survives continues to survive on further updates or merges? If so, you might want to consider persistentID implementation in MDM. Please clarify more on your use case.