User IDs longer than 40 characters are truncated in the Created by (sys_created_by) and Updated by (sys_updated_by) fields - Known Error

User IDs longer than 40 characters are truncated in the Created by (sys_created_by) and Updated by (sys_updated_by) fields Description If a user has a user name user_name longer than 40 characters, the values in the Created by sys_created_by or Updated by sys_updated_by fields are truncated when a record is created or updated.

The sys_created_by and sys_updated_by fields are of type varchar(40) on the Task table. The user_name field on the sys_user table is of type varchar(100).

Files attached to a new record by a user with user_id longer than 40 characters are not visible until after submit.

Steps to Reproduce

Create a user with a user ID longer than 40 characters. For more information, see the documentation topic Create a user . Impersonate the user. Navigate to Incident > Create New and create an incident. Personalize the Incident list to show the Created by and Updated by columns. Note that the user ID is truncated to 40 characters in the Created by and Updated by columns. What are the issues users with longer User Id’s will see? When users have a user_name longer than 40 characters they cannot download lists exported to Excel. When attempting to download, they are taken to a blank sys_attachment page. Users are unable to attach attachments from the service portal or normal UI to any record. After attaching the file and upload No attachments are added and not shown on the form. User will notice their name is truncated to 40 chars on activity stream for any record. 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.

A workaround would be to implement a modification on ACL script so that it validates the first characters of the records created in sys_poll.

NOTE: Make sure to test this in Sub-Prod instance before implementing in production. In this respective ACL on the Sys_poll table , change the script from:

answer = (current.sys_created_by == gs.getUserName());

to:

answer = gs.getUserName().indexOf(current.sys_created_by) > -1 ? true : false; so it checks the first 40 characters in the user_name and if it matches, it allows the attachment to be downloaded.