What we do in case it's Production with millions of records?
Thanks, Sandeep
S
Stéphanie FOURRIER
said
over 4 years ago
Hi Sandeep
Yes, in a Dev environment you can reset the matching by removing the data, tweaking your match rules or by adding a new match rule and then re-load the data.
Stéphanie FOURRIER
Can we reset Matches and run again on match rule change or add a new match rule?
The job used to reprocess the data can have
- Oldest First
- Popular
- Newest First
Sorted by Newest FirstStéphanie FOURRIER
The job used to reprocess the data can have
Preetish Anand
how to reprocess the match only
steps please
Stéphanie FOURRIER
For Production, please take a look at this Community article 'How to reprocess existing data in production to apply new rules':
https://community.semarchy.com/post/how-to-reprocess-existing-data-in-production-to-apply-new-rules-5f0f2479a9d20108f7bd5710
Stéphanie FOURRIER
Hi Peter,
What we do in case it's Production with millions of records?
Thanks,
Sandeep
Stéphanie FOURRIER
Hi Sandeep
Yes, in a Dev environment you can reset the matching by removing the data, tweaking your match rules or by adding a new match rule and then re-load the data.
Regards, Peter
-
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"?
-
Keep Melissa API calls under control during development
-
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
-
Which Golden ID survives when records are merged ?
-
Recertify with Existing Source Records in Integration Job
See all 48 topics