ServiceNow WashingtonDC API is giving different options sequence than other versions

[Int2E]

Hello Team,
For ServiceNow WashingtonDC, API's which provides us list as response has different options sequence as compare to other versions of servicenow(Vancouver, utah, etc.)

For Example: We are using an API for fetching prefix

https://service-now.com/api/now/v1/table/sys_choice?sysparm_query=name%3Dsys_user%5Eelement%3Dintrod...

Sequence of response in older version is : ["Dr.", "Mr.", "Mrs.", "Ms."] which is alphabetically ordered.
But is washingtonDC it is : ["Ms.", "Mrs.", "Dr.", "Mr."] 
Same behaviour we observe while fetching "Time zone", "Gender", "Date format", "Country code", etc. options from API.

Do we need to configure washingtonDC with some settings to achieve alphabetical order or this is the expected in case of washingtonDC ?

[Allen Andreas]

Hi,

You can pass additional query parameter such as: ORDERBYname, to help with the response sequence order.

Same as with ORDERBYDESC.

[Int2E]

@Allen Andreas I am aware about this ORDERBYname in the query but here I just want to ask whether is there a way to configure it on server because I can see for older version instances I am getting alphabetically ordered sequence without adding ORDERBY in API query or there unordered value are coming from serviceNow side only after some update which is specific to washingtonDC ?