Wrong storage of UUIDs when creating new M2A items

[cs-jbe]

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

We have a collection that has a child collection as a M2A relationship.
When adding new items to the child collection using the "Create New" button in the parent collection, the UUID of the newly created item is stored as a lowercase UUID in the relationship table. If you add an item with "Add Existing" instead, the UUID will be stored uppercase in the relationship table.

All items that are stored with a lowercase UUID in the relationship table cannot be edited via the parent collection. If you open such a new created item for editing, all fields remain empty.

This and similar behavior is also described in other issues. As soon as you edit all UUIDs in the relationship table to uppercase they are editable in Directus again.

We suspect that either the "Create New" button stores wrong UUIDs or an internal filter does not filter them correctly.

To Reproduce

Create tables "Movies" and "Actors". Add a M2A relationship to the "Movies" table referencing the "Actors" table.

Errors Shown

No errors shown.

What version of Directus are you using?

9.5.0

What version of Node.js are you using?

Directus Docker Image

What database are you using?

Azure SQL (MSSQL latest stable)

What browser are you using?

Chrome (97), Edge

What operating system are you using?

Local Windows / Azure Linux

How are you deploying Directus?

(Azure + Local) Docker

[rijkvanzanten]

Linear: ENG-271

[azrikahar]

I believe this is actually the same issue reported in #16671, especially since both are MS SQL specific and the same "symptom" of lowercased UUID(s) in M2A junction table. Since #16691 has resolved it, marking this as resolved as well 👍