When using the UNIQUELOV masking function in Fast Data Masker (FDM), users may observe that:
Fast Data Masker 5.0 and later.
This issue typically occurs because the Cross Reference identifier (specifically the rx_ref_id or the 'Cross Reference' setting in Column J of the mapping CSV) is missing or not configured correctly.
Even if the global options file includes the CROSSREFTABLE parameter and the connection to the XREF database is valid, FDM requires an explicit identifier in the mapping file to know which XREF 'bucket' to use. Without this, FDM defaults to an internal cache (DEFAULT_XREF) and does not write the new mappings back to the persistent external table.
To ensure consistency, you must enable and correctly identify the Cross-Reference setting within your masking configuration.
Update the Mapping File:
Verify Global Options:
Test the Configuration:
Consistency across masking jobs is only guaranteed when XREF functionality is explicitly enabled and assigned in the mapping file. For more information, refer to the .