Hey there! I encountered an issue while working early, and I feel the need to report it. Here’s the problem: you can’t add your most recently created collection as a relationship attribute to another collection if it’s listed as your 26th collection.
Let me break it down:
Scenario 1 (12 Collections): Suppose you have 12 collections. You want to add the last one (12th) as a relationship to any previous collections. The result will be successful.
Scenario 2 (26 Collections): Now imagine you have 26 collections. You want to add the 26th collection as a relationship. Unfortunately, it won’t appear in the options list.
P.S.: In Scenario 2, although you can search for the 26th collection, the selected field will remain empty.
This should only be a problem in the Appwrite console...and only if your filter for the related document doesn't find the document, right?
you don’t necessarily need to filter them. Mostly, if you scroll down the list, you will find your specific collection. However, in the case of the 26th collection, it won’t appear. But if you use a filter, you’ll get results, although they won’t be selectable
Oh NVM, I misunderstood the problem. Interesting....would you please create a GitHub issue?
That said, you can still create the attribute using a server SDK or the CLI
Sure,
Recommended threads
- Auth not working on expo react native
I'm trying to launch a development server with expo go and appwrite as a backend. On my windows pc, I've got a local docker instance of appwrite running as my b...
- Bulk delete failed with 401
- I created a transaction to bulk delete rows in a table has `done` equal `true` follow documentation. But when run, it returns 401 unauthorized error as screen...
- In which format should i pass the date?
I have a column with the type `datetime`. So i want to know which format is suitable for passing the date