Not able to commit update sets. Getting error as Commit called without update set id

[himanshusrivast]

I am importing my update sets in Kingston developer instance. After importing when I am trying to commit the update sets after preview, I am getting error as "Commit called without update set id". I got some errors and warning while preview on which I accepted remote updates but not able to commit it. Please help

[Vijay Talupula]

Hi Himanshu,

Please share the screenshot of error if possible.

Also just a thought in order to follow a best practice, Why don't you try to commit the update sets in other environments by creating Update Source and retrieve it and then proceed.

Retrieve an update set

[ayush_saxena]

Where you able to find root cause for this ?

[Tim Woodruff]

Hello, 

I just had a similar issue, and after a lot of troubleshooting, I found the problem. 

I'm not sure what the core issue was, but... When you commit a remote update set, the first thing it does is create a local update set record to hold the local update versions.
This was done, but somehow screwed up in my instance.

I had to delete not only the remote set, but the local version as well (with the same name), and then reimport the remote update set via XML, and redeploy it.

With any luck, this might solve your problem as well. 

[Mark Weaver]

Tim, 
I ran into a similar problem testing a deploy within a sandbox environment.  I had committed the update set once before.  When I deployed an updated version of the update set with the same name, I encountered this problem.  After deleting the one waiting in committing state and renaming the update set, all worked well when committing.