When a user is importing data from LDAP via a MID Server, the 'glide.import_set_row.dynamically_add_fields' property is set to true to make sure columns are created, but the column does not get created. Even after adding 'mobile' to the attributes setting in LDAP Server on the instance, the column still does not exist even though the attribute exists.
Steps to Reproduce
Connect the MID Server and LDAP Server:
- Create a MID Server.
- Create an LDAP Server with loaded users (approximately 50).
- Log in to your instance and ensure the MID Server connects to your instance correctly.
- On your instance, go to the LDAP Servers and create an LDAP Server to connect to your LDAP Server via the MID Server. It is important this goes via your MID Server.
- Set LDAP Server attributes to "cn,source,dn,facsimiletelephonenumber,givenname,l,mail,manager,objectClass,ou,roomnumber,sn,mobile,telephonenumber,uid,userpassword,manager"
- On the LDAP server, find a specific user (e.g. jsmith). Add an attribute called mobile and add the value +61429385774 for jsmith.
- Navigate to System Import Sets > Data Sources and create a new LDAP data source.
- Set the LDAP target to Users (RDN: ou=People). Set the other properties as required (name, etc.).
- Click Load All Records.
- Go to imported data and find user jsmith.
Expected result: This record should have the mobile column.
Actual result: The mobile column does not exist for anyone.
- Navigate to Systen Definition > Tables & Columns.
- Find and select the table LDAP User Import. A description for the table will be shown at the right side.
- The table will show the current columns available.
- Click on the Edit Table button.
- Under the Columns section, next to Table Columns, click New. This will open the dictionary entry.
- In the Type field, enter String.
- In the Column Label field, enter the same name as the attribute that you want to add in LDAP, and preserve the case. For example, "nylAgentCode".
- Click on the Max length Field (notice that the Column name field will be automatically populated) and set it to a value according to the maximum length for this attribute in LDAP side. Do not save the record yet!
- Click on the related link Advanced view. A new Attributes field will be displayed.
- Enter the following in the Attributes field: import_attribute_name=<attribute_name_here>
Note: <attribute_name_here> is the exact name of the attribute as it is in LDAP side. For example: import_attribute_name=nylAgentCode
- Click Update to update the record.
- Repeat these steps for each additional attribute desired in the import stage table.
Related Problem: PRB643379