Editing Closed Request Fields as Admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello Everyone,
I have an excel sheet of records data, and as an admin on Prod instance I want to be able to edit closed complete request fields which are read only to match with the excel I have, how do I do this in the best way with minimal manual work?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
40m ago
Hi @Elana
the best way to handle this is through an Import Set using a Transform Map.
Just go to Load Data, upload your Excel sheet, and create a Transform Map pointing to your target table (like sc_req_item or whatever request table it is). Make sure you set the ticket Number as your Coalesce field so the system knows to update the existing records instead of inserting new ones.
The most critical part for updating closed records: on your Transform Map record, make sure you uncheck the "Run business rules" box.
Also i want to highlight that modifying closed records in Production is considered a bad practice. Once a ticket is closed, it is supposed to be an immutable historical record. Changing data after the fact can skew historical reporting and potentially violate compliance audits.
Happy to help! If this resolved your issue, kindly mark it as the correct answer ✅ and Helpful and close the thread 🔒 so it helps other community members too.
Warm Regards,
Deepak Sharma
Community Rising Star 2025
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
33m ago
For minimal manual effort, you can use an **Import Set with a Transform Map** to update existing records from Excel.
- Identify the target table and the fields that need correction.
- Import the Excel file into a staging table.
- Create a Transform Map and use a unique identifier, such as the request number, with **Coalesce** to match existing records. Configure it for updates only so unmatched rows don't create new records.
- Before running the full import in Production, test a small sample in sub-production and verify the field restrictions and any business logic triggered by the update.
- After approval, run the controlled update in Production and validate the results.
**Important:** First confirm why the fields are read-only after closure. Don't disable OOTB Business Rules or security controls just to bypass the restriction.
FYR: Updating records using Coalesce
https://www.servicenow.com/docs/r/integrate-applications/system-import-sets/c_ImportSetCoalesce.html
Helpful? Please mark the response as Accepted Solution ✅ and close the thread — this helps future readers find the solution faster.
Regards,
Sachinvic
✨ ArchX Certified | ✨ 16x ServiceNow AI MVP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12m ago
Hi @Elana
I recommend using a standard Import Set and Transform Map while bypassing business rules and data policies, as this approach allows you to complete the operation securely in the background on the Production instance .
Probable Steps to be followed:
1. Prepare Your Excel Sheet: Ensure your Excel file includes a unique identifier for each request, such as the Number field, along with the specific columns corresponding to the fields you intend to update. This will help accurately identify and update the existing records.
2. Load the Data (Import Set)
3. Create the Transform Map
4. On the Transform Map form, uncheck the "Run business rules" checkbox.
5.Click Mapping Assist under the related links to visually map your staging table columns to your production target fields.
6. Set your unique identifier field (e.g. number) as the Coalesce field by marking its Coalesce column true
7. Run the transform
8. Ensure you are testing first it into your sandbox or non-prod like Dev and start testing with test load 20.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
