Currently if a mapped field is configured to be checked for data differences and that field is NULL in either the source or destination record but not the other, the field is flagged as a data difference. In some formulas it would be nice to be able to choose whether to consider NULL vs NOT NULL as a match for each field instead of always defaulting it to a data difference.
This is especially relevant when matching on Altru Alt Lookup IDs since those will often be NULL in Altru until they are first populated by an OIC formula.
Thanks for bringing this to our attention! We've got this on the slate to be researched, along with other ways we can improve the handling of common/consistent Data Differences.