Cannot add Collections to M2A-field

[fabianbeiermeire]

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 Collection "Pages" with a M2A-Field called "Content". When I created the M2A-Field I added two related Collections ("Headline" and "Text"). When I save the Page (in "Pages") everything works fine. But when I add a 3rd Related Collection ("image") to the M2A and add the new Content-Item "Image" to a page I get following error:

My M2A Relations:

I already found out that the Primary Key was not set, when adding the "Image"-Block

To Reproduce

Create a Collection with a M2A.
Add two item (Related Collections) to the M2A.
After initial saving of the M2A add more Related Collections to the M2A.

After that you cannot save the Collection with the M2A when an item was added that was later added.

Errors Shown

{ "message": "\"pages_content.item\" can't be linked to collection \"image", "extensions": { "code": "INVALID_PAYLOAD" } }

What version of Directus are you using?

9.0.0

What version of Node.js are you using?

v14.18.1

What database are you using?

SQLite 3.36.0

What browser are you using?

Brave (Chrome), Safari

What operating system are you using?

macOS

How are you deploying Directus?

running locally, Docker

[madc]

We see the same issue, I guess this is connected to #9182 (and #9315, #9438).

It seems, updates to M2A tables are not persisted. The app "remembers" the change and shows the new collection until a reload.

[fabianbeiermeire]

It seems, updates to M2A tables are not persisted. The app "remembers" the change and shows the new collection until a reload.

I see. I only realised that when I was restarting the local server it was gone. But you are right. Its also gone just after a simple Page reload.