- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 06:23 AM
Hi Community,
I'm trying to migrate a Standard Change Template from DEV to UAT using the Import XML method. During the import, I get the following error:
Skipping record for table std_change_record_producer and ID <sys_id> – permission denied
I'm not using an update set—this is a direct XML import. I've attached a screenshot showing the exact error message.
Has anyone encountered this before when importing to the std_change_record_producer table? Any idea what could be causing the permission denial during the import?
Appreciate any help or guidance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 09:08 PM
Hi @tilekarnilesh
That's the expected OOB behavior.
As a workaround you can try the below steps.
Community post: https://www.servicenow.com/community/itsm-forum/move-standard-change-template-to-another-instance/td...
How to migrate standard change templates across ServiceNow instances
- Export data from all these tables against your templates:
- std_change_template
- std_change_record_producer (where Template is your std_change_template)
- std_change_proposal (where Template is your std_change_template)
- sc_cat_item_catalog (where Catalog Item is Standard Change Record Producer)
- sc_cat_item_category (where Catalog Item is Standard Change Record Producer)
- std_change_producer_version (where template Standard Change Record Producer)
- You'll get access denied issue on std_change_template and std_change_record_producer so navigate to create ACL for these tables and check admin override true temporarily
- Import the xmls to all these tables
- Verify the change templates
- Revert the ACLs
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 11:24 PM
Thanks @J Siva I noticed that when records are aligned with a Standard Change Template, they need to be removed or deleted. After that, the import works fine. Thanks!"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 09:08 PM
Hi @tilekarnilesh
That's the expected OOB behavior.
As a workaround you can try the below steps.
Community post: https://www.servicenow.com/community/itsm-forum/move-standard-change-template-to-another-instance/td...
How to migrate standard change templates across ServiceNow instances
- Export data from all these tables against your templates:
- std_change_template
- std_change_record_producer (where Template is your std_change_template)
- std_change_proposal (where Template is your std_change_template)
- sc_cat_item_catalog (where Catalog Item is Standard Change Record Producer)
- sc_cat_item_category (where Catalog Item is Standard Change Record Producer)
- std_change_producer_version (where template Standard Change Record Producer)
- You'll get access denied issue on std_change_template and std_change_record_producer so navigate to create ACL for these tables and check admin override true temporarily
- Import the xmls to all these tables
- Verify the change templates
- Revert the ACLs
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 11:24 PM
Thanks @J Siva I noticed that when records are aligned with a Standard Change Template, they need to be removed or deleted. After that, the import works fine. Thanks!"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 11:55 PM
@tilekarnilesh
Glad it helped