Starting in Strategy Web 10, transaction input controls now have the functionality to obey the pre-defined report sort order of attributes, and to obey the custom sort specifed on an attribute form via the new Sort dialogue, like shown below:
When the sort behavior is set to Default, the transaction input control will obey the pre-defined sort criteria in the attribute. In some cases, this new behavior may result in a different element order between Strategy 10 and previous versions.
To understand the difference caused by this feature between Strategy Web 10 and previous versions, consider the following example where the source table for the List input control looks like this and displays the Player_City form:
50 | 50 | 50 |
50 | 50 | 50 |
50 | 50 | 50 |
50 | 50 | 50 |
50 | 50 | 50 |
50 | 50 | 50 |
50 | 50 | 50 |
50 | 50 | 50 |
In previous Strategy versions, the elements as they appeared in the List are ordered to show as:
While in Strategy 10, the elements will be ordered to show as:
This is because prior to Strategy 10, transaction services did not support sorting on transaction input control elements. Instead, element order was always determined by attribute ID. Starting in Strategy 10, the element order will obey the pre-defined attribute sort order by default. The pre-defined sort definition can be observed when opening the attribute editor in Developer. In the example above, if the Player attribute is sorted by Player_DESC ascending...
... then the List elements will be sorted as shown above with Cleveland at the top of the list (because Cleveland corresponds to Doug which is the first ascending Player_DESC).
Users have the option to modify this sorting behavior by explicitly setting the sort order on the List input control, like shown below:
Doing so will cause the list elements to be sorted independently of the sort order on the underyling dataset. For the example above, setting sort to be ascending by the ID form of the Player attribute results in the list being sorted the same as the pre-Strategy 10 behavior...
... where Miami is sorted first because it corresponds to the first ascending Player_ID.
KB242523
