Which Golden ID survives when records are merged ?
S
Stéphanie FOURRIER
started a topic
over 2 years ago
Which Golden ID survives when records are merged ?
Best Answer
S
Stéphanie FOURRIER
said
over 2 years ago
I see 2 situations where Golden records can be merged:
from a Merge or Split action in the UI: The lost golden ID record is the one that is dragged and dropped, for example:
from an External Load that updates or adds masters and makes existing golden merge together into a single one: The process takes the Golden ID of the following Master Records sort order:
B_CONFIRMATIONSTATUS = CONFIRMEDfirst
oldest B_CREDATE
smallest B_PUBID, B_SOURCEID
1 Comment
S
Stéphanie FOURRIER
said
over 2 years ago
Answer
I see 2 situations where Golden records can be merged:
from a Merge or Split action in the UI: The lost golden ID record is the one that is dragged and dropped, for example:
from an External Load that updates or adds masters and makes existing golden merge together into a single one: The process takes the Golden ID of the following Master Records sort order:
Stéphanie FOURRIER
Which Golden ID survives when records are merged ?
I see 2 situations where Golden records can be merged:
B_CONFIRMATIONSTATUS = CONFIRMED
firstB_CREDATE
B_PUBID, B_SOURCEID
Stéphanie FOURRIER
I see 2 situations where Golden records can be merged:
B_CONFIRMATIONSTATUS = CONFIRMED
firstB_CREDATE
B_PUBID, B_SOURCEID
-
Can we reset Matches and run again on match rule change or add a new match rule?
-
"Unmerge" records
-
Turn off match rules to speed up an integration job
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
How can I Configure Most Frequent Values in Survivorship Rules?
-
Deterministic or probabilistic matching
-
Machine Learning and AI for matching
-
Prevent loads from replacing values overridden by users
See all 40 topics