Incorrect data population

[ACripps]

Hi All,
We have identified incorrect data in the cmn_location table that appears to be originating from an external import. I suspect the LDAP User Import is the source; as shown in the attached image, the location is being mapped from the physicalDeliveryOfficeName field in the import configuration

Is there anywhere else i could be looking with a Target Table of Location (cmn_location) 

Thanks

[rafaelramos0]

Hi @ACripps !

This setting can definitely create new records in your location table. This is because the location field is referenced to the location table by the default setting.
You can unlink (delete this field mapping record) this field, but the user record will not have a location.
Another option would be to populate the location if the location record already exists, changing in field map record the "choice action" field to ignore.

Mark helpful if makes sense. 🙂

[ACripps]

Thank you for the response. I will liaise with my team with your response 😁