Update set crashed after linking application to source control

[Natalia Arvizu]

Context: We work with applications and each developer has one update set under their name. 

We have seen that when we link an application to the source control, then if we want to modify a variable or something else we get the message about the collisions: 

"This record has been recently modified in update set [Developer Name] by [Developer Name] but not committed to the source control (View differences). To edit the record use update set [Developer Name] or continue in default update set"

The update set is usually the one we have set, but seems like it's not "taking it".

Also when clicking on View differences, there's nothing to show. 

[Maik Skoddow]

Hi @Natalia Arvizu 

this is not a crash but an intended behavior and the underlying topic is called "collision avoidance".

See https://docs.servicenow.com/bundle/vancouver-application-development/page/build/applications/task/co... for more information.

Summarized: For a certain artifact (application file) different users made individual changes which have been tracked in different update sets. When linked to source control, ServiceNow introduces update sets which are named by the user. That way it is simulated that different users can work on the same artifact in parallel. And when submitting changes to the source control you will get offered all involved update sets from which you have to pick the right version of an artifact,

Maik

[Natalia Arvizu]

Hello @Maik Skoddow 

Thanks for the answer, the thing is that the element (policy, variable, script) has been modified in X update set, and we have set X as current update set. So that's where I'm confused about the message, I want to keep the property of avoiding collisions because I think that makes sense in general, but for such cases it's confusing because we have the proper update set selected.