Can't select many to one field in system filter UI

[LasseRosenow]

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

I have a recursive collection that has children of itself etc.

I have one special field that I only want to show, when the parent is null meaning on the root element. But its not working. I cannot select the parent field, because it only expands on click and shows its sub fields, but if I use a sub field and check for null of the sub field instead of the parent, it is not working either. Probably because it cannot check the sub field for null because the parent is null.

I want to select the marked field, but its not possible.

To Reproduce

Create a collection that has a o2m relation on itself and try to create a rule that hides some other field within the collection, if its parent is null.

Errors Shown

No response

What version of Directus are you using?

9.6.0

What version of Node.js are you using?

16

What database are you using?

MariaDB

What browser are you using?

Chrome, Firefox

What operating system are you using?

Windows

How are you deploying Directus?

On a remote Debian server

[abdonrd]

I think you should select the Parent > ID.

[LasseRosenow]

I think you should select the Parent > ID.

Yes I tried that but it did not work.

[abdonrd]

I have this one working:

[abdonrd]

Oh! Your are doing this in the Interface or in the Conditions?

In Interfaces it works for me, but in Conditions it doesn't.

[LasseRosenow]

oh I didn't know you could do it in the Interface :O

Yes I'm doing it in the Conditions ;)

[LasseRosenow]

But I can only use Conditions, because I want to hide certain fields that have nothing to do with the relation etc. meaning I have a Checkboxes field that I only want to show on the root element of my relational tree ;) I think that would only be possible with Conditions right?

[abdonrd]

Yeah, and it looks like a bug.

[rijkvanzanten]

But its not working. I cannot select the parent field, because it only expands on click and shows its sub fields

This feels like the underlying issue to me. Could you do me a favor, and try to see if it works if you edit the Raw Value (through the field label dropdown menu), and set the rule set in JSON manually?

If I'm understanding the use case correctly, it should be

{
  "parent": {
    "_null": true
  }
}

[LasseRosenow]

Yes this works

[rijkvanzanten]

Yes this works

Thanks for confirming 👍🏻

[abdonrd]

With this:

I have this in the raw value:

{
  "_and": [
    {
      "parent": {
        "id": {
          "_null": true
        }
      }
    }
  ]
}

And it works if I change it manually to:

{
  "parent": {
    "_null": true
  }
}

[rijkvanzanten]

It should also still work with the wrapped _and group:

{
  "_and": [
    {
      "parent": {
        "_null": true
      }
    }
  ]
}

The previous example (where you filter against parent.id) will validate that parent is an object with { id: null }, which (correctly) doesn't trigger in this case.

[abdonrd]

Yeah, looks like a UI/UX bug, right?

[rijkvanzanten]

Yeah, looks like a UI/UX bug, right?

Yeah! The "Parent" row in this case should be selectable as well, rather than just toggle its group open/closed.

[Nitwel]

Funnily enough, I remember that I fixed that issue already when I reworked the useFieldTree composable but someone must have set groups to be not selectable by mistake.

[rijkvanzanten]

Funnily enough, I remember that I fixed that issue already when I reworked the useFieldTree composable but someone must have set groups to be not selectable by mistake.

@Nitwel It only happens in system-filter, as it uses a v-select rather than a v-list with groups like we use in the display-template component 🙂 I created a new field-list component to standardize its use across the platform (mandatory xkcd) in #12157. Adding that field-list to the system-filter should resolve this issue as well 👍🏻

[Nitwel]

Oh I see, awesome!

[azrikahar]

Seems like this is the same as #12040, so closing this in favor of tracking it over there 👍