IBM Data & AI

Welcome to the idea forum for IBM Data & AI (Formerly Analytics) Clients! 


IBM Employees:

The correct URL for entering your ideas is



Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.


If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.


WEX - sortOrder API parameter does not function as expected

Alphabetical ordering of facet values - Supportanfragen - IBM Support The sort order of facet query result using REAT API does not change by the sortOrder parameter. For whichever order chosen, descendant order ("desc") or ascending order ("asc"), the facet order remains the same.

Example: The sort value facet parameter by descending or ascending (below URL’s) for REST API will produce the same output result:




REST API documentation for Watson Explorer Analytical Component (WEX AC) version 10 and above, as well as Watson Content Analytics ( WCA) version 3.5, explains that for facet query, sortOrder parameter exists. However, only descendant order (parameter value as "desc") is effective, as this is the default setting for the search query REST API. Changing the parameter value as ascending order ("asc") will not change the order of search result output.


  • Guest
  • Dec 14 2018
  • Needs review
Customer Name
Role Summary
  • Attach files
  • Admin
    YUTAKA MORIYA commented
    December 14, 2018 17:57

    Thank you for your input. Actually, the sorting parameters are limited.

    Moreover, let me quote this from Redbook.

    "Even if you select correlation as the default sort order, the list of facet values that are displayed are chosen by frequency. Therefore, if you leave the default of 100 keywords, you get only the 100 most frequent keywords. This means that sorting by correlation will not include values that are more highly correlated but not in the top 100 by frequency. This approach to sorting is by design, with the rationale that keywords with a very low frequency count would typically not be of interest. "

    So, even if the sortOrder parameter works (no matter it is sorted by correlation or labels), the entries in returned top K are sorted.
    Thus, the result is the same if your application sorts the returned value by itself. Could you consider if your application can sort the values to meet your requirement? If there is a specific reason you would like to receive the sorted list instead of sorting the entries by yourself, please feel free to add a comment.

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions