ADS_PersonAuto_Mapping_ADSAccount causes error message when importing ADSAccount.Title (128 chars wide) to Person.PersonalTitle (64 chars wide) (4318321)

ADS_PersonAuto_Mapping_ADSAccount causes error message when importing ADSAccount.Title (128 chars wide) to Person.PersonalTitle (64 chars wide), resembling:

[System.Exception] Error while assigning an employee to the AD user account ... System.AggregateException: One or more errors occurred. ---> VI.Base.ViException: Employees: Maximum length of Job description is 64. at VI.DB.Entities.ReadWriteEntityColumnImpl._PreSetChecks(Object value, Boolean throwExceptions) at VI.DB.Entities.ReadWriteEntityColumnImpl.SetValueAsync(Object value, SetValueBehavior behavior, CancellationToken cancellationToken) at VI.DB.Entities.PermissionsEntityColumnBase.d__5.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at VI.Base.SyncActions.Do[T](Func`1 function) at VI.DB.Sync.SyncEntityExtensions.PutValue(IEntity entity, String columnname, Object value) at DynScripts.ProductScripts_QsIMHzzpqKpiEz5BfODbsQixMBs.ADS_PersonAuto_Mapping_ADSAccount(String xObjectKey, String searchMode, String procId) ---> (Inner Exception #0) VI.Base.ViException: Employees: Maximum length of Job description is 64. at VI.DB.Entities.ReadWriteEntityColumnImpl._PreSetChecks(Object value, Boolean throwExceptions) at VI.DB.Entities.ReadWriteEntityColumnImpl.SetValueAsync(Object value, SetValueBehavior behavior, CancellationToken cancellationToken) at VI.DB.Entities.PermissionsEntityColumnBase.d__5.MoveNext()<---

WORKAROUND

In 7.0.1, the column length can be altered manually for Person.CentralAccount (to 110 chars), Person.PersonalTitle (to 128 chars) and Person.ZipCode (to 40 chars). Since the change is included for the next release, such a change is migration safe.

STATUS

Development has acknowledged the behaviour as bug #24560 and fixed it for the next release after 7.0 SP1.

The information in the script(s) provided is known to work successfully; however, they have not been officially tested by One Identity Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by One Identity Support and Development.  One Identity Support and Development recommend always making a backup of the current database prior to execution of any script(s) that may modify it. For customization of Identity Manager, please contact our Professional Services Organization.