FDM masking is not masking all records in the source database

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Observing that a few of the values are skipped from masking, but the logs and audit have no information on it. Have seen this issue before while masking SQL Server DB. 

Environment

FDM version: 4.10.536.0
TDM Portal: 4.10.217.0
SQL Server Data Source

Cause

Looking at the masking configuration provided, and the log, noticed that using a WHERE condition for the SQL Server table in question. Suspect that the unmasked rows don't match the WHERE condition, and therefore they are not masked.

Keep in mind that when using a WHERE condition - it applies to each and every masking rule BELOW the line with WHERE condition, until end of file, or a different WHERE condition is found for the same table; no matter how many masking rules for other tables are between.

For Example: The WHERE condition that is applied on TABLE2 will apply on COLUMN1 and COLUMN8 in the masking rules below.

Table	Column	Function	Parm1	Parm2	Parm3	Parm4	Keep Nulls	…
TABLE1	COLUMN1	FORMATENCRYPT					Y
TABLE2	COLUMN4	FORMATENCRYPT					Y
TABLE2	COLUMN1	WHERE	NAME NOT IN ('{','}','*****','...', ' ', '********','=','&','}}}')
TABLE3	COLUMN5	HASHLOV	Generic Details	7			Y
TABLE4	COLUMN2	WHERE	ADDRESS NOT IN ('{','}','*****','...', ' ', '********','=','&','}}}')				Y
TABLE2	COLUMN8	FORMATENCRYPT					Y

Resolution

If this is not what was intended, and wanted to mask all rows in the table and column in question, will need to move that masking rule up in the masking mapping.csv file, before the masking rule containing the WHERE condition.

Check the rows that were not masked, do these rows meet the WHERE clause applied? If not, then that is the reason it was not masked.