Survivorship rule: change golden record status attribute to INACTIVE when all master records have the same status.
Cedric Blanc
a créé un sujet
sur un an il y a
I currently have a Survivorship rule where the golden record status field is equal to the most recent update of a master record status field. I want to change this to a Survivorship rule where the golden record status field should be changed to 'inactive' only when ALL master records have inactive statuses. If one master record becomes active, the golden record is active. Can you help with this?
Meilleure réponse
C
Cedric Blanc
a dit
sur un an il y a
What you can do is to set your Status attribute value using a Post-consolidation only enricher.
Set the expression using this SemQL :
CASE WHEN ALL IntegrationMasterRecords HAVE (Status = 'INACTIVE' )
THEN 'INACTIVE'
ELSE
'ACTIVE'
END
1 commentaire
Cedric Blanc
a dit
sur un an il y a
Réponse
What you can do is to set your Status attribute value using a Post-consolidation only enricher.
Set the expression using this SemQL :
CASE WHEN ALL IntegrationMasterRecords HAVE (Status = 'INACTIVE' )
THEN 'INACTIVE'
ELSE
'ACTIVE'
END
Cedric Blanc
I currently have a Survivorship rule where the golden record status field is equal to the most recent update of a master record status field. I want to change this to a Survivorship rule where the golden record status field should be changed to 'inactive' only when ALL master records have inactive statuses. If one master record becomes active, the golden record is active. Can you help with this?
What you can do is to set your Status attribute value using a Post-consolidation only enricher.
Set the expression using this SemQL :
Cedric Blanc
What you can do is to set your Status attribute value using a Post-consolidation only enricher.
Set the expression using this SemQL :
-
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
Voir tous les 33 sujets