To synchronize a Microsoft Active Directory/LDAP field value to your WordPress plugin field, you must create a mapping. A mapping is an individual data synchronization instruction.
Each mapping is evaluated at the run time to assure the data is moved correctly from a Microsoft Active Directory/LDAP server source to the target plugin entity.
To complete a mapping, you must select a target WordPress field, the primary LDAP field and optionally one to many secondary LDAP field(s).
If you want to set a constant value for a WordPress field, you can use "Use Default Value Only" option of the primary LDAP field dropdown and set a default value for the mapping.
Before you map fields, it is important to follow the best practices below.
You can set one to many secondary LDAP fields in your mapping to provide a fall back value for the corresponding primary LDAP field.
If the primary LDAP field of a mapping is empty or null, Microsoft Active Directory/LDAP addon checks the secondary LDAP field(s) to see any value available to assign.
If multiple secondary fields are set, the value assignment is based on the order of the secondary field(s). For example if you select field A first and then field B, the value check is completed based on the field A first then the field B.
If the secondary field(s) and the default value of a mapping are both filled out, the value of a set secondary LDAP field(s) gets validated first before the default value is assigned.