Issue with Default Update set for custom applicationIssue A custom application usually uses its own update set to pass the application configurations to other instances easily. The issue users encountered is that the custom application, specifically in its development environment (DEV), is missing the default update set for this particular custom application. This absence of the default update set leads to complications when attempting to update the custom application, as any changes made are then passed to the global default update set instead.CauseEither this is caused by a system property, or this is a global application. It will not have any default update set for itself and user Default(global). At some point in time, this application underwent a change in its configuration, transitioning from a custom application to a global application. This change could have occurred either during its initial creation or through a subsequent update. As a result, the application now operates on a broader scale, affecting all users and systems, rather than being limited to specific custom settings.ResolutionUsers would likely want to check the scope of the application first: A global application will not have any default update set for itself and will use Default(global).Once the scope is out of global and says it's part of the custom scope for the app, then everything should behave as expected.For more information, see: Global scopeGlobal application file management Attempt to convert the app from global to scoped: As an example, create a new scoped app for PM Human Resources and move the data over to it (maybe by XML export and imports). If the Application Scope is not global and it's within its own custom scope, then users would want to check out this property to see if it solves the issue: The system property glide.ui.vcs.collision_avoidance is usually enabled by defaultTry setting the property to false