Cannot commit Update Set 'Default' because: Update scope id 'global' is different than update set scope id '88b99145db323300174d9235ca9619a6'. Resolve the problem before committing.

[dhathrianoop]

I'm getting below error , while moving the update set.. how to fix the issue

Cannot commit Update Set 'Default' because: Update scope id 'global' is different than update set scope id '88b99145db323300174d9235ca9619a6'. Resolve the problem before committing.

[Alikutty A · Accepted solution]

Hi,

Why are commiting the Default update set? The error says there is an update with sys_id "88b99145db323300174d9235ca9619a6" in it which is from a different scope and hence it cannot be committed.

You will need to Skip this specific update or remove it from your update set and then commit it again. If you need to move update "88b99145db323300174d9235ca9619a6", then recapture it in the correct scoped update set and move it once again.

Thanks!

[Ashvini Kadus1]

Hi dhathrianoop

Which version your working?

might be your one instance that you have worked on is different than the one instance that you are moving your update set.

please check both the versions or release version.

because this issue was caused by an old UI Action i.e "Export to XML" on the update set form. The solution is to revert the UI action to the another instance release version, where you trying to commit this update set.

i believe its a scoped application that you are work on. because in release versions this function has been replaced by the "publish to store" action for scooped application.

Kindly mark correct or helpful if it helps you to solve your problem.

Thank You,

Ashvini k

[Priyanka22Yadav]

Hi Ashvini,

Update set uploading will not get affected due to the instance change. This issue is due to the record get created in different scope application that related records scope application.