When attaching variable set(s) to a catalog item, the user can edit the order in the related list. The expected behavior is the following:
If the order is not specified, the order is inherited from what is specified in the variable set.
If the order is specified, it overrides what is defined in the variable set.
Separate variables defined for the catalog item and their order work in conjunction with the ordering for variable sets. Refer to the attached screenshot named Order-Logic.JPG for an overview.
The behavior works well in Eureka earlier than patch 7. For patches later than patch 6, the ordering for the single variable is always be placed on top (effectively an order of 1 regardless of what you defined). The order of the variable sets does not seem to be inherited. Compare the attached files Eureka-6-n-below.JPG and Eureka-7-n-above.JPG.
Steps to Reproduce
- Create two variable sets.
- Set 1 should have an order of 1000
- Set 2 an order of 50
- Include a few variables of your choice in each set
- Associate the sets to a catalog item.
- For set 1, leave the Order empty
- For set 2, set the order to 1
- Create a variable on the catalog item.
- Assign an order of 200
- On the catalog item, click Try it.
The expected order on the catalog item is:
The actual order on the catalog item is:
The ordering of the variable sets should respect the order defined by the many-to-many between the variable set and the item. If some of the many-to-many records have an order, then the records with no order are listed first. The remainder are then ordered by their value. If the order field for all many-to-many records is empty, then the order defined on the variable set record itself is used.
For more information, see Define Variable Set Order.
Related Problem: PRB629653