[BUG]: Ordering parameter in API (Tasks-Table)

[gpascal123]

f, for example, you sort by Dispatched/Searched, the table is initially sorted correctly. If you switch to another page and then back again or reload the tasks page, the following error message appears.

Error in the API:

Error occurs when sorting by

• Name (parameter taskName)
• Dispatched/Searched (parameter clientSignature)**

[gluafamichl]

I think the problem is an incorrect dataKey in tasks-table.component.ts (line 139). The dataKey 'clientSignature' does not exist in the Tasks table, that's why the PHP backend correctly throws an exception. Currently I can't see, what the correct dataKey for this table column should be, what information is displayed in this special column?

[gluafamichl]

Just checked the old PHP UI, Dispatched/Searched column is excluded from sorting, maybe that's the correct solution for the new UI, too?

[gluafamichl]

We have to check all tables in the new Web UI, there are quite a lot of mismatches in the dataKey settings (key names do not exist in Backend DB tables) Sounds like a perfect bug to add some more unit tests ;-)

[gluafamichl]

Will be checked again when reviewing new paging backend API.

[ObsidianOracle]

Frontend has to be compatible with the api before checking the ticket again

[gluafamichl]

All unknown dataKeys set to isSortable: false, sorting only works for backend keys from database