Can you batch update sets from multiple applications?

[Patrick Laroch1]

Hi,

We have features that included updates to multiple applications (Global and CSM), is it possible to have one batch update set for the release or do we have to create one batch update set per application?

[Christian_]

Hello,

Asked myself this question, as this is something I want to do now.
Haven't tested this myself, but with that said, it should be possible. See accepted solution here.

[Allen Andreas · Accepted solution]

Hi,

Just came across this thread and wanted to provide some information:

-While you "can" have multiple application updates within the same update set, upon promotion to another environment, you will receive an error that you have a different application update within a set that is supposed to be for another application (as update sets are declared per application upon creation).

-What is recommended and what people normally do is create a parent update set within the Global Scope, then create your children update sets within their own respective applications, capture the updates, and set the parent for those children update sets to the parent global update set.

-Export the batch (can only do so from the parent global update set)

-Import to another environment and preview from the parent global set

-Commit

[Allen Andreas]

Hi,

I just wanted to check-in on this. If my reply above helped guide you correctly, if you don't mind, please mark it as Helpful & Correct.

Thank you!

[JG16]

Unfortunately , it did not work out. 

I have parent Update Set in Global scope and in that  I have few child Update Sets are from  APM (Application Portfolio Management) application scope. 

I have tried by exporting and importing. It thrown the different scope error.

Thanks

JG

[Allen Andreas]

Hi,

I'm not sure what all you had going on, but if you're saying you had a parent update set in Global, and a child update set from another scope and you exported from the parent...the batch set (which includes the parent and the child set)...and promoted that to another environment and you got errors for different scope...then something else is going on on your end.

You can have a parent and child from different sets. This is how it's supposed to work....and it does work because I do it every day, haha.

So inside one of those sets you're talking about...you most likely have mixed scope updates (meaning in the child set for 'x' scope you have at least 1 customer update inside that is from a different scope). I'd recommend taking a look at that and correctly it, then trying again.

Please mark reply as Helpful/Correct, if applicable. Thanks!