Fields are truncated at 40 chars on initial LDAP load via MID Server - Known Error

Fields are truncated at 40 chars on initial LDAP load via MID Server Description When creating a data source for LDAP that uses a MID server, the Import Set is created with fields of length 40 characters, even when the sample 20 records exceed that length for those fields.

Steps to Reproduce

As a prerequisite, follow the procedure in Create a data source for LDAP to create a New Data Source for an LDAP Server configured to use a MID server.

1. Navigate to System LDAP > LDAP Servers. 2. Select the LDAP server to configure. 3. In the LDAP OU Definitions related list, select an item, such as Groups or Users. 4. In the Data Sources related list, click New. 5. Complete the Data Source form (see table). 6. Click Submit. 7. Under Related Links, click Test Load 20 Records to test whether the data source can bring LDAP data into the import table. 8. After the import is complete, select "Loaded data" to review the data. 9. Check the fields that should contain more than 40 chars. Observe these have been truncated.

Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologize for any inconvenience.

As a workaround, setting the system property “ com.glide.loader.verify_target_field_size ” to true during the initial load allows the fields to automatically be resized as the data is loaded. Once the initial load is completed, it is recommended to set this property back to false to avoid any future performance issues that may occur from a column being resized on a table that contains a large amount of data. We would also suggest reviewing the fields in the Import Set and manually setting them to a larger value than needed to accommodate future data that may exceed the current size.