Discard/Ignore Records Below Certain Threshold
It would be really nice if we could ignore records below a certain threshold in both the 1:1 and 1:N matching and in all instances. The current feature in 1:N seems like a great idea, but it doesn't work. It will only ignore records below a certain threshold if there are records that are higher than that. For example, my threshold is set to 72% on one of my formulas. It doesn't work on 1:1, only 1:N. And it only works on 1:N when there is an 87% match that pulls in at the exact same time. Otherwise, all of the 71% or 50% or whatever matches come through as they are the "highest" and so the system ignores my request to ignore those.
Breanne Leach
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
-
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