Batch Update Set

johnrob18
Giga Guru

We have a batch update set containing 3 child records. This has been migrated from Dev to Test.

We now have an additional update set in Dev that we want to put in the release.

I have made the new update set a child of the parent in Dev.

I have then tried to import the update set from Dev to Test (all update sets are still in Complete state on dev) and it has not imported any of the changes that I have made.

How can I get the 'new' update set from Dev to Test?

It does not seem that the 'new' update set has been imported with the new parent - how do I get this across?

4 REPLIES 4

Andrew Barnes -
ServiceNow Employee
ServiceNow Employee

Greetings Johnrob,

 You need to perform your batching prior to moving to another instance, or do the batching in the 2nd instance for the additional item. So, remove the parent from the update set in dev, goto test, retrieve, preview, commit. Now the local update set in test can be set to have the parent to the batch parent you intend. This assumes you will pull the update set from test to the next instance. 

Please let me know if you have any questions about this process.

-Andrew Barnes
Join me at Developer Blog

 

Hi, I have removed parent in dev, gone onto test - retrieve, preview and commit but only part of the update set has been applied. so most of the change has not been applied to the test environment.

How do I get around this?

 

find_real_file.png

 

 

 

What wasn't loaded? The only thing i see is the version error, which is likely because there is newer version info in test than was in your update set.

Hi Andrew,

I tried to work with batch updates since few changes. However, I'm stuck in the scenario provided here by @johnrob18. I'm using SN Orlando. Here is the scenario:

  1. I had a batch base with 2 child update sets in DEV
  2. I set them both as "completed"
  3. I moved them all to the TEST / UAT instance
  4. Now I've a fix in DEV (#4 - see below screenshot)
  5. I put it as "completed" and move it to TEST
  6. Before committing the fix in TEST, I tried to set the batch base or its child update set as parent, but couldn't. It's because they are already committed. When I do it, I get this error message:
    find_real_file.png

On the other hand, I tried to set this child / parent relationship in DEV, but when I do it then I can't retrieve the batch base anymore from TEST, except if I delete it from there. This is anyway not a good practice.

 

Would you be able to bring light on this ?

 

Best regards

Julien