Update Set includes changes from app not installed in prod – potential issues?

[davidbaur_]

Hi all,

We have three instances: dev, test, and prod. A ServiceNow Integration app from the Store is installed on dev and test, but not on prod.
On test, we've decided the app doesn't suit our needs and plan to uninstall it. However, we still have update sets on dev and test that include changes to tables from the Connector app.

Our concern: if we move these update sets to prod, will we run into issues since the app was never installed there?

• Will ServiceNow ignore those records because they're in a different application scope?
• Or should we manually exclude or clean up those update sets?

Has anyone faced a similar situation? Appreciate any input!

Thanks,
David

[Mark Manders]

Never move anything you don't want to move. Even if you wouldn't get errors and they would be ignored, you should NEVER move anything to PROD that you don't need/want there. Clean up your update sets.

But you mention that the app is in a different scope. So that means that your updates to the tables are in update sets of that scope. Just put them on 'ignore' so they can't be moved at all.

[Ankur Bawiskar]

@davidbaur_ 

2 ways

1) keep whatever is present in the update set and let the error come for those customer updates -> you can skip the update

2) If you are batching up then simply remove the update sets belonging to this app scope from your parent update set (Recommended way)

If my response helped please mark it correct and close the thread so that it benefits future readers.