Choices on a scoped form become part of a global choice set

[aaron_k]

Someone please tell me if there's a better way to do this. I had to work out this procedure in order to push these changes in an update set. If there's no better way, maybe this will help someone out.

In order to create or alter choices in a particular dropdown on a form in a scoped application (and have it tracked in an update set that will commit):

1. Create a Global scoped update set.
2. Create an update set in the scope of the application.
3. While in the application scope, using the scoped update set:
   1. Creating and modifying choices should be done from the choice list view using the form to create new choice records.
   2. Updating the order of the choices on the form should be done from the configure choices view off the form field.
4. Once changes are done, go into your scoped update set.
5. For each update (should be of type Choice list):
   1. Go into the update and select the Show Related Record link at the bottom.
   2. See that the scope on the Choice Set is Global.
   3. Go back to the update and change the Update set field to the Global scoped update set you created in the beginning.

Your Global scoped update set is the one you'll push to your other instance.

Using Jakarta

[lkleijn]

I have the exact same problem using Istanbul. When I want to create a choice from a scoped application, it creates the choice but puts it in the GLOBAL scope AND in a SCOPED update set which means I run into errors when migrating my update sets to other instances. Any fix on this ?