- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 04:19 AM
Hello everyone,
Here's the scenario: I have a ServiceNow instance for QAS, from which I pull all the completed update sets from another DEV instance by pressing the "Retrieve Completed Update Sets" button in the "Remote Instance" form.
The issue I'm encountering is with a specific Update Set that was marked as completed in the DEV instance, retrieved, and committed in the QAS instance as usual. However, after committing the Update Set in QAS, the developer realized there was a small change to be made. They reopened the Update Set in the DEV instance, added the modification, and completed it again.
Now, since the Update Set was already committed, the QAS instance does not import it again. Consequently, the developer created another Update Set to transfer that change to QAS, raising a few questions:
If the Update Set was NOT committed yet in QAS (only previewed), would it be imported again with the new change added by the developer?
Is there a way to force or "re-import" the Update Set in QAS, even if it has already been committed?
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 05:13 AM
1. No. The update set is already retrieved and that is why it is the absolute worst practice to reopen an update set. Never ever do that.
2. You can delete the committed update set and run a new retrieve. It will then get the 'new' update set and you can commit it.
Both aren't to be advised. Just create a new update set, retrieve it to QAS and batch it to the previously retrieved update set, so it can be moved to PROD as one.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 05:13 AM
1. No. The update set is already retrieved and that is why it is the absolute worst practice to reopen an update set. Never ever do that.
2. You can delete the committed update set and run a new retrieve. It will then get the 'new' update set and you can commit it.
Both aren't to be advised. Just create a new update set, retrieve it to QAS and batch it to the previously retrieved update set, so it can be moved to PROD as one.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark