Scoping when committing update sets

[Patrick71]

Wanted to share a bit of knowledge I learned today. When adding a record to an update set manually, it doesn't capture the application scope you are currently in. Thus, when you bring that update set into another instance, you need to be in the same scope as your update set, otherwise those updates will throw a scope discrepancy error. I committed an update set in a scoped app today, which contained manually added data. However, I was in the global scope while previewing, and got those errors. Switching to the same app scope allowed me to commit the update set.

[Sid_Takali]

Hi @Patrick71 Thanks for sharing your knowledge. It is pretty much Helpful for us.

Regards,

Siddharam

[JayBhavsar]

@Patrick71

So, this only applies for update sets that have manually added records?

Is it true that update sets that are recorded in let's say "Scope A", when committing to higher instance, can they be committed in the Global Scope? Will the updates be moved properly in their respective scopes?

Also, is it true that update sets with different scopes can be included in the same batch update set? Does that work when committing the batch update sets to higher instances?