Survivorship rule: change golden record status attribute to INACTIVE when all master records have the same status.
Cédric BLANC
started a topic
about 4 years ago
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?
Best Answer
C
Cédric BLANC
said
about 4 years ago
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 Comment
Cédric BLANC
said
about 4 years ago
Answer
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
Cédric 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 :
Cédric 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?
-
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"?
-
Prevent loads from replacing values overridden by users
-
Keep Melissa API calls under control during development
-
Existing records and match/merge changes in app builder
-
Where are Matching Details of User Merges (and splits)?
-
Is there any built in xDM functionality that allows you to report on data differences between two points in time?
-
Enrich existing records
See all 53 topics