When you import market data in Market Pricing > Compensation Market Data, Dayforce maps the data records according to the mapping set up for the selected market data definition in Market Pricing > Market Data Definition.
If one or more of the mapping fields is left blank in the import file, Dayforce considers those fields a match regardless of what is included in the employee's profile and will map to the employee if all of the other mapping fields also match.
For example, if the State column is used for mapping, but the field is left blank for a market data record in the import file, that record is considered a match for all employees whose primary work assignment includes a state (regardless of which state that is).
If you want to ensure that mapping is only applied when employee data matches the market data exactly, you should enter NULL for the fields in the import file that are missing data. Fields marked as NULL are ignored during mapping and aren't considered a match unless the corresponding value in the employee's profile is also Null.