"Default 1" Updateset got created

puneetgoels1
Tera Guru

I created a new updateset and when I closed it, a new updateset got created with the name "Default 1" in global domain. Where as "Default" in global domain was already there and is "In Progress". Earlier I have noticed, if I close an updateset, "Default" updateset used to got set but this time, it created this new updateset "Default 1" and set it. 

 

Any ideas, why did it happen?

 

1 ACCEPTED SOLUTION

DScroggins
Kilo Sage

Hello,

 

The reason this is happening is when you set the Default update set to Complete or Ignore the system will create a new update set automatically. Also when this happens there is a flag on the update set Default set which gets set to false and it gets set to True on the newly created set. This flag is what determines the actual Default update set. You will not only need to put the original Default set back to In Progress you will also need to set the flag Default set back to true. Only one update set per application scope can have that flag set as True. Hope this helps.

 

find_real_file.png

 

--David 

View solution in original post

8 REPLIES 8

Jaspal Singh
Mega Patron
Mega Patron

Just make sure that 'Default' update set of Global scope is not Ignored/Complete. As its only after state being Ignored/Complete Default 1 will be set automatically.

DScroggins
Kilo Sage

Hello,

 

The reason this is happening is when you set the Default update set to Complete or Ignore the system will create a new update set automatically. Also when this happens there is a flag on the update set Default set which gets set to false and it gets set to True on the newly created set. This flag is what determines the actual Default update set. You will not only need to put the original Default set back to In Progress you will also need to set the flag Default set back to true. Only one update set per application scope can have that flag set as True. Hope this helps.

 

find_real_file.png

 

--David 

actually this happens whenever you have any update set selected other than the default one, and change the state of your selected update set to complete while it is selected. in this case it will not automatically go back to the default update set but just create a new one called default 1, 2 and 3, etc. really annoying indeed. not sure if this is by later design or a bug, but didn't use to be like this in the past. maybe a business rule triggered by on change of update set state may help if you can make it always select the default one when completing the current selected update set.