Matching and Scoring Logic
When triaging records with 1:N (many) matches, it would be nice if there would be a way to implement different tools to facilitate auto matching... * use fields for matching that are NOT mapped -- match on a custom field in the destination system that is NOT even in the source system... * use fields for triage (scoring) that are NOT mapped for data synch... - might want to apply a score on an updated date field but this field is not mapped. * scoring rules - there are other salesforce deduping tools that provide the ability to assign points for each type of match. * match types -- points for oldest record vs newest -- points for a field = to or greater than or contains or starts with... * auto match on score? -- auto select a winner based on highest or lowest score... can choose if you auto accept the scored winner or you just default to a winner in the comparison grid * manual review - which fields to show to help determine which record is a best fit -- allow the user to select which helper fields to show in the comparison screens happy to walk through how other systems do this...
Jeff Herron
shared this idea
We have released a new feature to Omatic Cloud called Advanced Matching Settings. By prioritizing the search scenarios, Advanced Matching Settings can help reduce the number of records that are returned when searching the destination system. This feature will:
-Save time when sorting and reviewing records during routing.
-Reduce the number of API calls to your endpoint.
-Exclude unlikely matches if better matches are found.
You can learn more about setting up these settings in our User Guide: https://omatic-cloud.helpdocsonline.com/matching$advanced-matching-settings
In addition, you can match to records based on fields even if they are not mapped (including defined fields), as long as they are available in the specific endpoint for matching. If there are specific fields you are looking for that aren't available, feel free to create a new idea for those fields. When reviewing the grids, the summary review fields enable you to select which additional fields you would like to review in the comparison screens.
Here are some other ideas specific for auto-pick logic. You can vote on these ideas, or add a new idea for anything that wasn't covered by the recent updates.
https://omatic.uservoice.com/admin/v3/ideas/46297843
-
We have released a new feature to Omatic Cloud called Advanced Matching Settings. By prioritizing the search scenarios, Advanced Matching Settings can help reduce the number of records that are returned when searching the destination system. This feature will:
-Save time when sorting and reviewing records during routing.
-Reduce the number of API calls to your endpoint.
-Exclude unlikely matches if better matches are found.You can learn more about setting up these settings in our User Guide: https://omatic-cloud.helpdocsonline.com/matching$advanced-matching-settings
In addition, you can match to records based on fields even if they are not mapped (including defined fields), as long as they are available in the specific endpoint for matching. If there are specific fields you are looking for that aren't available, feel free to create a new idea for those fields. When reviewing the grids, the summary review fields enable you to select which additional fields you would like to review in the comparison screens.
Here are some other ideas specific for auto-pick logic. You can vote on these ideas, or add a new idea for anything that wasn't covered by the recent updates.
https://omatic.uservoice.com/admin/v3/ideas/46297843
https://omatic.uservoice.com/admin/v3/ideas/46298224