I have created a matcher to find duplicate record and when i try to persist the data through rest api, I get the following message with status as PERSIST_CANCELLED :
My requirement is to update the existing record when the match is successful without throwing error as duplicate.
Could you please help me to resolve this.
Thanks.
Best Answer
B
Bharat Joshi
said
over 3 years ago
When you try to persist the data and it throws validation error because in your payload you have activated 'ALL validations' & All match rules,because When a user creates a new record, and the DETECT_DUPS validation is active, the matcher is used to search for similar records in order to warn the user when a new entry matches existing records. So, you can remove those two lines from the payload for both employee and registration entity then it will work fine and update the data without throwing error
1 Comment
B
Bharat Joshi
said
over 3 years ago
Answer
When you try to persist the data and it throws validation error because in your payload you have activated 'ALL validations' & All match rules,because When a user creates a new record, and the DETECT_DUPS validation is active, the matcher is used to search for similar records in order to warn the user when a new entry matches existing records. So, you can remove those two lines from the payload for both employee and registration entity then it will work fine and update the data without throwing error
Asha.ramegowda
I have created a matcher to find duplicate record and when i try to persist the data through rest api, I get the following message with status as PERSIST_CANCELLED :
{
"validationType": "DETECT_DUPS",
"validationName": "$DUPS_COLLISION",
"validationErrorMessage": "Person>DETECT_DUPS>$DUPS_COLLISION"
}
]
My requirement is to update the existing record when the match is successful without throwing error as duplicate.
Could you please help me to resolve this.
Thanks.
When you try to persist the data and it throws validation error because in your payload you have activated 'ALL validations' & All match rules,because When a user creates a new record, and the DETECT_DUPS validation is active, the matcher is used to search for similar records in order to warn the user when a new entry matches existing records. So, you can remove those two lines from the payload for both employee and registration entity then it will work fine and update the data without throwing error
Bharat Joshi
When you try to persist the data and it throws validation error because in your payload you have activated 'ALL validations' & All match rules,because When a user creates a new record, and the DETECT_DUPS validation is active, the matcher is used to search for similar records in order to warn the user when a new entry matches existing records. So, you can remove those two lines from the payload for both employee and registration entity then it will work fine and update the data without throwing error
-
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