Why is the user id exceeds the configured length of 40 and was displayed properly in the user table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2022 10:51 PM
Hi ,
We used Azure Active directory to provision users in our instance . There are users with more 40 chars in their user id .
We have an instance rome version and the user id was capture and displayed correctly even though the config max length of user id is 40.
On the other hand we have a tokyo instance using the same Azure active directory but the user id is cut to the length or 40 chars only .
Does someone encountered this also in their instances ?
Regards,
Edgar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2022 11:03 PM
Hey @Edgar10,
from my point of view this was a bug in Rome which was now fixed.
It is the normal behavior that field values (not only the user id but all fields) will be cut by ServiceNow during the insert based on the configured max length.
You just have to adjust the user id max length on the table and your import will work again.
Best regards
Oli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2022 11:54 PM - edited 12-21-2022 11:56 PM
Hi Oliver ,
Could you share some reference that is a bug ?
Also it is not advisable to increase the length of the userid. See below KB
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0870001
Regards,
Edgar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 12:10 AM
Hey Edgar,
not really, no.
It is just a common thing I know from my work in the past years.
Best example is if you import e.g. an excel file and create the import table automatically.
If your cell in excel has something written with more than 40 characters it will be cut because ServiceNow will create the import table fields with 40 chars max length.
Best regards
Oli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 12:14 AM
Hi Oliver,
I agree 100% for other fields but specifically for user id it is not recommended.
Per KB here's the Cons.
What are the issues which can arise by increasing the max length of the user ID field?
The User IDs will be truncated to 40 characters when they are stored in the Created by and Updated by fields. This can lead to seeing values that look the same if the first 40 characters of different User IDs happen to be the same. That can raise various issues such as:
* Confusion among users
* Reports and filters returning incorrect results
* Failing ACLs
* Flow Designer flow getting stuck when the Run As field is set to 'User who initiates session'
* etc.
Users with a User ID longer than 40 characters will also not be able to attach files to a record.
Regards,
Edgar
