- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 07:26 AM
Hi all,
We had a reference field on incident table which refers to User table.
Our requirement got changed, and I converted type of that field to List type (refers to user table only)
Now, if I add multiple users to that list field and save the form , it will just keep 1st user added and will clear others automatically.
Not sure what is the reason behind it. Has anyone faced similar issue?
Please let me know if it is because I changed the type of field or anything else?
Thanks in Advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 07:42 AM
Hi @BijoyDeb ,
Check the Max length value of the dictionary(field) and increase it if it is set as 32 and try.
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 07:42 AM
Hi @BijoyDeb ,
Check the Max length value of the dictionary(field) and increase it if it is set as 32 and try.
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 08:04 AM
Hello @BijoyDeb
It seems like the issue is related to the field type. When you change a reference field to a List type, the system doesn't automatically adjust to allow multiple values.
Try changing the field type to Glide List. This allows the field to handle multiple users while still referencing the User table. Here's how you can do it:
Navigate to the dictionary entry for the field (sys_dictionary table).
Update the field type to Glide List.
Ensure the Reference field is set to sys_user.
Save the changes and test.
This should resolve the issue. Let me know if you need further assistance!
If this helped, please hit like and mark it as an accepted solution. It helps future readers to locate the solution easily in community.
Thank You
Juhi Poddar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 08:30 AM
Yes it's because of field type change and it might have some inconsistency.
If the field is not in TEST or in PROD then delete that field in dev and create new list type field and use that
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader