Could not find a record in sys_atf_test for column test referenced in this update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Could not find a record in sys_atf_test for column test referenced in this update
all steps got same error what should i do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi Venkatasai,
This error typically occurs during an Update Set preview when the target instance is missing a parent ATF Test record (sys_atf_test) that a subsequent update (like a test step) refers to. Essentially, the system is trying to update a test or link a step to a test that doesn't exist on your current instance yet.
Common Causes
- Missing Parent Record: You may have captured a test step in your update set, but the actual ATF Test record it belongs to was either not captured or was included in a different, uncommitted update set.
- Incomplete Migration: If you manually moved records via XML or separate update sets, the dependency order might be incorrect.
- Deletion in Source: If the test was deleted and recreated in the source instance, the sys_id references in your update set may be broken
How to Fix It
- Identify the Missing Sys_ID: Open the Update Set preview error to find the specific sys_id of the missing sys_atf_test record.
- Export/Import via XML:
- Go to your source instance (where the test was created).
- Navigate to the sys_atf_test table, find the missing record, right-click the header, and select Export > XML.
- In your target instance, navigate to any list, right-click the header, and select Import XML to upload the file.
- Re-run Preview: Once the missing record is present, go back to your Retrieved Update Set and click Run Preview again; the error should resolve.
- Consolidate Update Sets: If you find multiple missing dependencies, consider merging your update sets on the source instance to ensure all parent and child records are captured together before re-exporting
Hope this helps! If it answers your question, please consider marking it as Helpful or accepting it as a solution.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
it clearly says you have captured the Test Steps but didn't capture the Test in your update set
Please verify your update set and re-capture that and then preview and commit.
💡 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 || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
This error usually come when target instance not find related reference record.
Probable fix:
a. Create a update set In Dev and make it current.
b.Open up the list view of all your Tests (that you want to capture in the update set)
<your instance name>.service-now.com/sys_atf_test_list.do?sysparm_query=&sysparm_view=
In bulk, change the Active flag to false, then change back to true. Now that we updated the record, they will definitely be in the update set.
Or
using force to update set related link one by one capture in update set
c. Now first commit this update set to your other instance
d. Then you try to commit the update set where you were getting error
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi
This error usually come when target instance not find related reference record.
Probable fix:
a. Create a update set In Dev and make it current.
b.Open up the list view of all your Tests (that you want to capture in the update set)
<your instance name>.service-now.com/sys_atf_test_list.do?sysparm_query=&sysparm_view=
In bulk, change the Active flag to false, then change back to true. Now that we updated the record, they will definitely be in the update set.
Or
using force to update set related link one by one capture in update set
c. Now first commit this update set to your other instance
d. Then you try to commit the update set where you were getting error
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti