I have two collections: workspaces and workspace_membership. The workspaces collection has a one-to-many relationship. When I attempt to add a member to the workspace document via the workspace_membership collection, I receive an error message:
Here’s the schema for the workspace_membership collection:
{
"$id": "workspace_membership",
"$createdAt": "2025-01-08T08:54:55.354+00:00",
"$updatedAt": "2025-01-08T08:54:55.354+00:00",
"$permissions": [],
"databaseId": "dbid123",
"name": "workspace_membership",
"enabled": true,
"documentSecurity": false,
"attributes": [
{
"key": "user_id",
"type": "string",
"status": "available",
"error": "",
"required": true,
"array": false
},
{
"key": "role",
"type": "string",
"status": "available",
"error": "",
"required": true,
"array": false,
"elements": ["OWNER", "ADMIN", "MEMBER", "GUEST", "VIEWER"],
"format": "enum",
"default": null
},
{
"key": "status",
"type": "string",
"status": "available",
"error": "",
"required": true,
"array": false,
"elements": ["INVITED", "ACTIVE", "EXPIRED", "REVOKED"],
"format": "enum",
"default": null
},
{
"key": "invited_at",
"type": "string",
"status": "available",
"error": "",
"required": false,
"array": false
},
{
"key": "accepted_at",
"type": "string",
"status": "available",
"error": "",
"required": false,
"array": false
},
{
"key": "workspace_id",
"type": "string",
"status": "available",
"error": "",
"required": true,
"array": false
}
],
"indexes": []
}
What should I do to resolve this issue and correctly link the member to the workspace document?
Note: This issue only occurs when I try to add a member to a workspace. All other relationships are working fine.
Recommended threads
- proccessing problems
A database schema operation is stuck in my Frankfurt project. In the matryq database, the workspaceId attribute of the coaching_activity_entries collection rema...
- User column is processing
I am still encountering the processing tag after creating a column in my database. and its not a network or refresh issue, i have refreshed over and over, shutd...
- Custom API domain is unreachable
Earlier my custom api domain was working fine. Now it seems to be offline without a trace a few hours later. I didn't change anything, all the relevant DNS reco...