Sorting doesn't work on a field that is relational

[alan-cleveston]

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

When trying to sort a field that has a relationship, the sorting does not work, if the field is an input it works normally.

To Reproduce

To reproduce the error just use a relational field in a content and try to sort

ORDENACAO.SEM.FUNCIONAR.mp4

Errors Shown

No response

What version of Directus are you using?

9.5.2

What version of Node.js are you using?

16.14.0

What database are you using?

Postgres 13.4

What browser are you using?

Chrome

What operating system are you using?

Linux

How are you deploying Directus?

Docker

[licitdev]

The API correctly wrongly returns the sorted values of an M2O.

Screen.Recording.2022-02-21.at.11.47.39.AM.mov

[licitdev]

This issue ended up being more complex through testing as the sorting needs to be done on the rendered values. It affects displays such as related-values, translations and other custom displays for the following types: ['m2m', 'm2o', 'o2m', 'translations', 'm2a', 'file', 'files'].

@rijkvanzanten Should sorting be disabled for the above listed types?

[rijkvanzanten]

@licitdev There is no way to sort on a o2m, as there is no value to sort on. M2O's are currently sorted on the actual saved value, which might be different from the displayed value.

The improvement here is to implement/finish #4502, and then dynamically use that when sort is being used on a column that's relational and has a related-values display 👍🏻

I'll close this for now in favor of #4502, as it's a new feature request that already exists, rather than a bug