|Subject:||Comparing LDAP values with truncated RT values leads to history bloat|
LDAP values longer than the RT field length will be truncated upon update. Afterwards, all subsequent comparisons to see if the field needs to be updated from LDAP will indicate that LDAP has a new value since the length differs. The result, however, is that the same value ends up in the database once truncated, and user history is bloated. LDAP values should be truncated to the RT field length before being used for comparison. This information *should* be accessible via - Show quoted text
>_Accessible.Refer to for an example.