What happens to old golden records when a new master record merges with existing goldens?
A
Anna
started a topic
3 months ago
Let's use the CustomerB2CDemo tutorial environment and dataset.
Day 1: I loaded Wesley with source record ID CRM.1365204.
This creates a new golden record with ID 15069.
Day 2: I loaded 3 new source records which are duplicates CRM.1422971, CRM.1398375, MKT.1379005 (see the spreadsheet attached to this topic). These duplicates master records match and merge with the Wesley record with source record ID CRM.1365204.
A new golden ID is created on the golden record 8a035.
In the MI table, I see that the CRM.1365204 record has an b_oldsdpk with the old golden ID, 15069. This makes sense to me because the 15069 golden record no longer exists.
The customer wants to know what happened to the old golden record. Does xDM send the old golden record to the GX table for delete? Or does xDM update the golden record to reflect the new golden ID and the new consolidated values?
Old golden record is moved to GX table for deletion because that golden record became legless (if all the master records of a golden record are deleted, the golden record becomes legless and is automatically deleted. Golden-record deletion supports the deletion propagation defined in the reference relationships.).
1 Comment
T
Toshish Chauhan
said
3 months ago
Answer
Old golden record is moved to GX table for deletion because that golden record became legless (if all the master records of a golden record are deleted, the golden record becomes legless and is automatically deleted. Golden-record deletion supports the deletion propagation defined in the reference relationships.).
Anna
Let's use the CustomerB2CDemo tutorial environment and dataset.
Day 1: I loaded Wesley with source record ID CRM.1365204.
This creates a new golden record with ID 15069.
Day 2: I loaded 3 new source records which are duplicates CRM.1422971, CRM.1398375, MKT.1379005 (see the spreadsheet attached to this topic). These duplicates master records match and merge with the Wesley record with source record ID CRM.1365204.
A new golden ID is created on the golden record 8a035.
In the MI table, I see that the CRM.1365204 record has an b_oldsdpk with the old golden ID, 15069. This makes sense to me because the 15069 golden record no longer exists.
The customer wants to know what happened to the old golden record. Does xDM send the old golden record to the GX table for delete? Or does xDM update the golden record to reflect the new golden ID and the new consolidated values?
Old golden record is moved to GX table for deletion because that golden record became legless (if all the master records of a golden record are deleted, the golden record becomes legless and is automatically deleted. Golden-record deletion supports the deletion propagation defined in the reference relationships.).
Toshish Chauhan
Old golden record is moved to GX table for deletion because that golden record became legless (if all the master records of a golden record are deleted, the golden record becomes legless and is automatically deleted. Golden-record deletion supports the deletion propagation defined in the reference relationships.).
-
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 43 topics