- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2025 01:00 PM
I accidentally changed the field type from reference to string for the "location" field on the Task table while working on the Change table. Now, I'm trying to change it back by manually changing it or reverting to the previous version, but I keep getting a message stating the following: "Type change not allowed. Invalid type conversion for field 'location' on 'Task.' Cannot convert from 'String' to 'Reference.' There exists data records (1471) that are not a Sys ID.
Does any one have any suggestions on how to revert this back to a reference field?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2025 01:33 PM
Hello @Daniel Arnold
I think the only way to go here is now to run a bulk update on the location table - populate the sys_id in place of names in the fields and then change it to reference.
It's coming because reference fields search for sys_id but after converting to string there is only name left which is obviously not a sys_id. So this will work.
Also, if you have a copy of this in any other instances, then export the dictionary xml from there and try to import. If that doesn't works, then this bulk update to sys_id is the way to go.
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2025 01:05 PM
Not sure how much helpful
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0695947
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2025 01:33 PM
Hello @Daniel Arnold
I think the only way to go here is now to run a bulk update on the location table - populate the sys_id in place of names in the fields and then change it to reference.
It's coming because reference fields search for sys_id but after converting to string there is only name left which is obviously not a sys_id. So this will work.
Also, if you have a copy of this in any other instances, then export the dictionary xml from there and try to import. If that doesn't works, then this bulk update to sys_id is the way to go.
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY