#Possible bug: deeply nested query attributes not properly parsed in admin?
1 messages · Page 1 of 1 (latest)
Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:
Documentation:
That's the broken one, here's the working one:
these where's are generated by the exact same resusable filter object
It seems like the main difference is it's one more level down in the where clause (these are complex nested "ands")
Whats more, the query that produces this API call in admin works totally fine in a local API find