LDAP import maps LDAP import maps match fields in your LDAP database to fields in your instance. Note: LDAP mapping has a performance effect, so the recommended approach is to schedule it during off-peak hours, or process a few records at a time to maintain system availability. The best practice is to define a transform map that only imports the needed or required attributes. Depending on the version of the instance you are using, the method for specifying LDAP mapping relationships varies. The easiest way to know whether or not you are running a version which uses the System LDAP application for LDAP integration is to find the application from the application navigator. The Run Business Rules option is applied only for the target table. Only transform maps associated to the target table run the business rules associated with different tables. If you are updating a user group and have business rules running on a user group table, the group must have roles define. Table 1. LDAP import mapping options System LDAP application? Map Yes Use a transform map to specify your mapping. No Use a LDAP legacy import map to specify your mapping, or the default LDAP transform that is included in baseline instances. Remember to adjust the Coalesce field to match against the correct fields. Differences between LDAP transform maps and legacy import mapsWhen specifying LDAP mapping relationships using transform maps, there is a major difference in how reference fields are set for manager and department. LDAP import default mappingIf you do not specify a transform map (such as LDAP User Import), the integration uses the following default mappings.LDAP scriptingThese sample scripts automate common LDAP tasks. Verify LDAP mappingAfter creating an LDAP transform map, refresh the LDAP data to verify the transform map works as expected. Record creation options during an LDAP transformAdministrators can specify when to create new records based on changes from incoming LDAP records.