Skip to main content

Hi,

We have a subject definition with a default sort order on three columns and a prefilter which is always on (logged on user specific content filter). When this subject is opened from a menu-item, it shows the records in the correct (subject defined) sort order.

When this same subject is accessed using the API, it seems to have a different (or no) sort order. When looking at the request Universal sends to Indicium using the same endpoint, all sort columns are specified in the request.

Is my assumption correct that the sort order, which is defined on the subject level, is not used when accessing the resource through the endpoint without any parameters? Or is there some setting that can be used. It would be preferred to use as much the subjects configuration where possible so it only has to be coded in the backend.

Hi Robert,

The model definition is used by Universal to call the API of Indicium in the preferred way. Indicium will not apply sorting automatically when simply retrieving all table data. The sorting must be given with the request URL.

Hi Mark,

Thanks for the reply. That makes it clear why the external consumer get’s another sorting order than defined at the subject level.

Terms & ConditionsCookie settings