Missing Update Set [Needit Application]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2019 07:18 AM
Hi, I'm facing an error where every time that I tried to switch to my applications scope it use the global scope.
I notice that my app was using the Default[Global] Update set, so I went to my Local Update Sets list and there was not Update Set for my aplication, however, there was an Update set with an empty Aplication, odd at least.
I tried to create a new one, but since the application field is auto populate and read only (and I'm using the Default Global Update set), I can't change the 'Global' value,
So.. My Application is from the learning path, so no big issue, but I'm certainly curious about how this happened, How can avoid it and how can resolve it.
Thanks!
- 2,149 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2019 11:15 PM
Hi,
Have you created an application from Global?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2020 12:53 PM
I am also stopped by this problem, and see many instances of it in the forums. I still don't know what an update set is, but it's clearly very important. As such, why do they keep vanishing? That seems a serious bug that should be fixed. The fact that replacing them seems complicated and dangerous reinforces that this should not be such a common problem. Why does this happen? Is there any easy fix that doesn't risk blowing up the whole instance as I've seen indicated?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2020 07:37 AM
Hi Yadin,
Did you get this sorted, ran into the same issue?
Thanks
Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2020 08:50 AM
Support partially resolved it in so far as they accidentally caused a new Update Set to be created with their poking around. While they didn't realize they did that (or advise how to finish fixing the issue given it was still not functional) once I saw that existed I was able to go in to the application context then make it my default set. At that point it relinked things and stayed working. The update set says it was created by the support person instead of system as expected, but that doesn't seem to matter. They have yet to be able to explain why this happened or really detail the issue in any way, like what he did to accidentally make the update set exist when forum posts indicate that's a complex process.