We noticed when we configure the "Associate" button on an object grid in a task view, the default sort order of the grid results are on System Fields.Name, even if that field is not visible in the grid.
IBM support confirmed that this is working as expected (always sorting the results by default on System Fields.Name, even though the field is not visible in the grid).
Would be great and more intuitive for users if it would default sort on the first visible column in the grid instead.
An example use case would be Employee objects that are autonamed. The autoname has no meaning for the end user. Only the First Name and Last Name fields. But when they summon the Employee picker to select employees, even if Last Name is the first grid column, they appear to not be in alpha order at all because they are being sorted by default on the autoname that is not even visible.
Current workaround is simply a training issue that users have to click on the first column heading in the picker to dynamically sort the available object alphabetically on the Last Name field.
|Needed By||Not sure -- Just thought it was cool|
Do not place IBM confidential, company confidential, or personal information into any field.