Added fall-back duplicate check fields for all entities

Last update:
Created :
Written by Thomas Speekenbrink

Overview: 

We added fall-back duplicate check fields for all entities. If the first check cannot be executed due to an empty field, then the second field is used

How to:

On every entity that supports duplicate checking a secondary duplicate check is now available. This check will come into effect when the first check is skipped. The first check will be skipped if the value that is checked on is empty. For example:

db2.png

If the row in the source file now has empty ‘VAT No’ the first check is skipped and the secondary duplicate check is executed. So, there will be a check on company name, instead of VAT No.
Important note: the secondary check is not used as a fallback when the first check does not yield any results (if no match is found).