- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I got below error when I tried to move an update set include flow design, how can I resolve it?
Error: Could not find a record in sys_hub_flow_version for column version_record referenced in this update
Solved! Go to Solution.
- 1,001 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @pathumharsh
This article provide you all details.
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
since the zurich release added the new flow designer versioning table (sys_hub_flow_version) and flow records now reference a version_record that isn’t automatically captured in update sets........ the preview breaks on the target instance because the referenced version doesn’t exist there......so you must include the actual sys_hub_flow_version record in the update set (for example by exporting/importing it or using create application file) or remove the version_record tag before preview.......otherwise the missing version causes the error until servicenow provides a proper fix......
If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.
Kaushal Kumar Jha - ServiceNow Technical Consultant/Developer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
this is a known issue, check this KB and will be fixed in Zurich Patch 5, Australia release
the below KB has the workaround as well for fixing
sys_hub_flow_version record of the flow is not getting captured in Update set when updating the flow
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @pathumharsh
This article provide you all details.
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
since the zurich release added the new flow designer versioning table (sys_hub_flow_version) and flow records now reference a version_record that isn’t automatically captured in update sets........ the preview breaks on the target instance because the referenced version doesn’t exist there......so you must include the actual sys_hub_flow_version record in the update set (for example by exporting/importing it or using create application file) or remove the version_record tag before preview.......otherwise the missing version causes the error until servicenow provides a proper fix......
If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.
Kaushal Kumar Jha - ServiceNow Technical Consultant/Developer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
this is a known issue, check this KB and will be fixed in Zurich Patch 5, Australia release
the below KB has the workaround as well for fixing
sys_hub_flow_version record of the flow is not getting captured in Update set when updating the flow
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi Ankur, i see patch 5 is now available can you confirm it's been fixed in this patch?
Thanks
