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]

Did you mark the original update sets to ignore? I'm not sure if that will resolve it but it's worth a try. If it doesn't, check the record that is missing and just confirm it's in place once you've committed your update set.

[tee3]

I had already previewed them as 3 separate update sets before I merged the sets and previewed it and I cannot mark them to ignore at this point.

As for checking after committing, I have 148 warnings. It'll be quite the task to check them. I'm wondering if I should Accept or Skip the updates in the warnings?

[Dubz]

You can delete them and set them to ignore at the source.

If you're confident you have everything in your update set you need then commit, these are warnings not errors so there shouldn't be any required action.

[tee3]

Thanks Dave!

[bernyalvarado]

Hi tee,

You can always accept the update. Since the reference is composed of a sys_id of a record that will later be committed you will not have any issues.

Thanks,

Berny