isOrder Attribute - Is It Functional and Current?

[dppedersen]

I am trying to set the default search order for a table (any table, although I specifically need it to work for kb_knowledge) by using the isOrder attribute. Documentation suggests the following:

"An administrator can set the sort order of records displayed for a table in the system dictionary when there is no other sort specified. This is done by adding an attribute called isOrder with a value of true to the dictionary entry of the desired field. This sort is the sort order presented to all users initially. Once a user sorts a list, that user preference is saved, and the list is always sorted for that user based on the previous sorting preference.

Note: isOrder can define which field is used for list sorting, but cannot control the sort direction."

https://docs.servicenow.com/bundle/kingston-platform-administration/page/administer/list-administration/concept/c_ControlTheListSortSequence.html

However, documentation also does not list isOrder as an active dictionary attribute, nor is isOrder present in the sys_schema_attribute table:

https://docs.servicenow.com/bundle/jakarta-platform-administration/page/administer/reference-pages/concept/c_DictionaryAttributes.html

Further, adding isOrder=true to any sys_dictionary entry in Incident, Problem, or Change, seems to have no effect on any default sorting, even when user preferences for sorting are deleted.

In conclusion: is isOrder an active attribute? With active functionality?

[Brad Tilton]

It is still active. I tested it on a custom table with a new user so I didn't have to worry about user preferences and it appears to work. It's possible there could be something else happening with the extended task table hierarchy and table flattening there that would cause it to work differently in that case.

[Pamela Johnson]

I was hoping to use this attribute, but it apparently doesn't exist in my instance. Any suggestions on how to establish a default sort order for the list view of a table? I have a field named "Order" that I intended for this purpose. Thanks!