Update Set Preview Problems.

[tee3]

I'm wondering if anyone has run into this before. I have 3 update sets, all created one after the other for one project lets say. They have all been tested in QA and are ready to be moved into PROD, I retrieve them, preview them and now I have warnings in all three along these lines: "Could not find a record in sys_security_acl referenced in this update, but did find it in another uncommitted update set"

My problem is that when I look at the uncommitted update or update set, it's in one of the other two update sets. How can I resolve this?

https://docs.servicenow.com/bundle/helsinki-application-development/page/build/system-update-sets/ta... suggests that I commit the other update set first but in my case the other update set has the same warnings pointing to the first update set.

Any suggestions will be highly appreciated!

[Dubz]

Can you not merge the update sets? Then you'll just have 1 set to commit.

[Ankur Bawiskar]

Hi Tee,

This error says that the other update set has the reference but not yet committed. Are you sure they were one after the other.

If you are sure that this problem will be addressed in next uncommitted update set then you can skip from current and note it down somewhere so that you remember this step.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.

Thanks

Ankur

[Jaspal Singh]

Hi Tee,

Unless these are not error I don't think there would be an issue. If it says error then look for the update set that has those update commit it & then things would work well. Else best option is to merger all those updates & then commit it.

[tee3]

Thank you everyone for your replies.My next step was to merge them and apply to PROD but now that I have done so, I get the same warnings on the merged set. Not sure if that will cause re-work. Any ideas?

Here is an example of the warnings I'm getting: