
I have a collection that is related to the user account so it has a userId
attribute that I use to store the user's ID. A user should only have one record for this collection but I can't seem to make this userId
attribute the primary key for the collection. It always creates a document ID that I need to reference. I know that I can always get the document first by searching the userId
- and then use the document ID from there to update the values of the document but I was hoping there would be a better way to do this.

What you can do is to set the document ID as the user ID and then you have the primary key uses the user ID.

Oh you mean when I create the document, instead of using ID.unique()
, I'll use the user ID instead.. I don't know why I didn't think of that. Thank you!

Does that solves your issue?

Yes it does. It was my bad for not thinking of such a simple solution.

Great! 😁

[SOLVED] How to update a document without knowing the document ID?
Recommended threads
- Sharing cookies
Hi, I’m using Appwrite Cloud, and I have a setup where my Appwrite backend is hosted on a subdomain (e.g., api.example.com), while my frontend (Next.js app) and...
- Organization not exists anymore
Hello! We have a problem with a cloud database. We are on the Free plan, but after a refresh the site wants me to create a new organisation, and I not see the c...
- JSON and Object Support in Collection do...
I am working with Next.Js and Appwrite Cloud, I am relatively New to Appwrite but i have noticed there is no direct support of JSON and Object support in attrib...
