Prevent loads from replacing values overridden by users
Cédric BLANC
started a topic
over 2 years ago
How can you setup Semarchy so that any user edits to golden records will "stick"? For example, if a user determines that a golden phone number is invalid and deletes the golden phone number, a future load will just put the phone number back
Best Answer
C
Cédric BLANC
said
over 2 years ago
In the Survivorship Rule for that attribute, you need to set an 'Override Strategy' under Override Rule. The strategy is 'Override - until next user changes'. This means that values coming from the publishers consolidate according to the Consolidation Rule. But when an override is made, the value changed by a user always takes precedence and is maintained until a user enters a new value.
1 Comment
Cédric BLANC
said
over 2 years ago
Answer
In the Survivorship Rule for that attribute, you need to set an 'Override Strategy' under Override Rule. The strategy is 'Override - until next user changes'. This means that values coming from the publishers consolidate according to the Consolidation Rule. But when an override is made, the value changed by a user always takes precedence and is maintained until a user enters a new value.
Cédric BLANC
How can you setup Semarchy so that any user edits to golden records will "stick"? For example, if a user determines that a golden phone number is invalid and deletes the golden phone number, a future load will just put the phone number back
In the Survivorship Rule for that attribute, you need to set an 'Override Strategy' under Override Rule. The strategy is 'Override - until next user changes'. This means that values coming from the publishers consolidate according to the Consolidation Rule. But when an override is made, the value changed by a user always takes precedence and is maintained until a user enters a new value.
Cédric BLANC
In the Survivorship Rule for that attribute, you need to set an 'Override Strategy' under Override Rule. The strategy is 'Override - until next user changes'. This means that values coming from the publishers consolidate according to the Consolidation Rule. But when an override is made, the value changed by a user always takes precedence and is maintained until a user enters a new value.
-
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
See all 44 topics