Fields Don't Respond to Conditions Set In M2O Fields

[supermx1]

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

hk.mp4

To Reproduce

See above video

Errors Shown

None

What version of Directus are you using?

9.5.2

What version of Node.js are you using?

14

What database are you using?

MySQL

What browser are you using?

Chrome, Brave

What operating system are you using?

MacOS, Ubuntu 20.08LTS

How are you deploying Directus?

Digital Ocean Cloud

[azrikahar]

Duplicate of #10952, and we are currently tracking this in #8228 so feel free to follow the notification over there 👍

EDIT: See also #11844 for most recent related discussion.

Just as a summary, the general issue with M2O condition revolves around the condition set is actually:

{
    "m2o_field": {
        "id": {
            "_eq": 2
         }
    }
}

but when we are selecting an item of m2o field, the condition that is actually expected by the app is:

{
    "m2o_field": {
        "_eq": 2
    }
}

hence the condition couldn't match properly.

[ulvidamirli]

Duplicate of #10952, and we are currently tracking this in #8228 so feel free to follow the notification over there 👍

EDIT: See also #11844 for most recent related discussion.

Just as a summary, the general issue with M2O condition revolves around the condition set is actually:

{
    "m2o_field": {
        "id": {
            "_eq": 2
         }
    }
}

but when we are selecting an item of m2o field, the condition that is actually expected by the app is:

{
    "m2o_field": {
        "_eq": 2
    }
}

hence the condition couldn't match properly.

I try this with the latest version (9.8.0) but it doesn't work. My problem is the same as the OP. Could you please help to solve this?

[rijkvanzanten]

@ulvidamirli You already posted in #8228 too, so lets keep the conversation in there 👍🏻