Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App: Sorting current collection by using a nested field throws an error #15914

Closed
ALAiello opened this issue Oct 7, 2022 · 1 comment
Closed
Labels

Comments

@ALAiello
Copy link

ALAiello commented Oct 7, 2022

Describe the Bug

Expected
When using a nested field in a collection to sort it, it should sort the collection correctly by nested field.

Actual
When using a nested field in a collection to sort it you get an error message

To Reproduce

Add translation to a collection
Add field to translation
Create element of collection
Create multiple translations for field
Go to App and add nested field of translation to table
Sort by nested field => probably nothing happens
Reload page => see error

Errors Shown

[INTERNAL_SERVER_ERROR] select "article"."isFaq", "article"."status", "article"."id" from "article" where not "article"."status" = $1 order by "izrgb"."title" asc limit $2 - missing FROM-clause entry for table "izrgb"

What version of Directus are you using?

  • 9.18.1 (Cloud)

What version of Node.js are you using?

  • Cloud

What database are you using?

  • Cloud

What browser are you using?

  • Chrome

How are you deploying Directus?

  • Cloud
@joselcvarela joselcvarela changed the title sorting current collection by using a nested field App: Sorting current collection by using a nested field throws an error Oct 7, 2022
@licitdev
Copy link
Member

licitdev commented Oct 7, 2022

Sorting of nested multi relational values in O2M fields such as translations is currently unsupported. Ref: #13239
PR #14798 attempts to add support for the sorting of such multi relational values.

@licitdev licitdev closed this as completed Oct 7, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants