Rijk van Zanten

@andy1li You're correct. That being said, I believe the change in this PR might be a solution for (unconfirmed) bug #14571, so I don't wanna close it yet 👍🏻

> Create a Many to One field with that One to Many field as foreign key. This feels incorrect to me. The one-to-many (o2m) "field" is an alias, not a...

What was the exact configuration for the o2m field? What foreign key were you using?

Ref https://github.com/directus/directus/pull/14311

Sweet! > Do you think that my approach is valid or it can cause some issues? Great question.. It's a very "core" update that will affect basically _everything_, so there's...

I'll ping you on discord 🙂

> Just as a note from #14717 : this also happens on Directus Cloud and when we 'force' a field to become a foreign key by mentioning it as a...

> I think this stems from a deeper problem that required fields aren't validated at all in the backend. Using the REST API, you can both insert new records and...

> Maybe it's because that object is an array with multiple user id's? But in the docs example it seems to be possible with emails... What is the correct syntax?...

@br41nslug There's tons of other issues/discussions that are effectively riffs on the same problems: 1. Validation runs against the _submitted payload_, not against the merged result of existing data +...