Catalog item & question choices on update sets.

[Brad Campbell]

Hi All,

I am very new to the ServiceNow world and work in an organisation which is just about to go live next week. I have been working with update sets but tend to create everything first before adding to the set. I am moving service catalogue request items from dev to Test but have noticed that where I have variables of the "choice type" (Select Box and Multiple Choice) it doesn't carry over the choices, just the variables themselves.

Is there a way to include these rather than having to go to that level within the variable form to add them? This will be quite time consuming especially since we are going to be pushing around 100 + forms to production in the coming days.

Thanks in advance!

Brad

[Ravi Peddineni]

@Brad Campbell 

That should not be the case. Everything should be captured in the update set. Might happen that they are captured in default set. Please verify the versions.

[Brad Campbell]

@Ravindranath It works on both Default and a personal update set if you have selected the update set first before creating the request so that it records everything you do. But in an example below where I used the Default and tried to add the entire item after it was created it leave out the question choices.

This was using the "Add to Update Set" UI button.

Thanks

Brad

[Mohamed Rahim1]

The cause of this is that probably what you are doing is that you create the catalog items, add all the variables and then change your update set to the one that should contains these updates!

the problem with this approach is that you only capture the records when you click update meaning that when you create a catalog item you update multiple records on multiple tables not only a single table.

the right approach to capture your work on an update set is to actually set the update set as your current update set, start building your catalog item and then review all the updates captured on this update set, otherwise these updates will be captured in the global update set and it will be so confusing to move the changes and pick the appropriate updates and move it to the right update set.

hope this helps! 

[spike]

I've had a similar problem. If you're using the catalog builder and capturing the updates in an update set, what gets captured isn't always correct. This is a known issue with the way the catalog builder saves and deletes temporary items as it publishes the item (the wrong sys_id gets captured in the update set). ServiceNow say it'll be looked at and fixed at some stage in the future..