
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
- Query params are way too limiting in ter...
I was trying to list rows in a table that do not already exist in another table. I retrieved around 260 row IDs which are 13 characters in length each, and then...
- Relationship null, even when relationshi...
Hi Everyone, im experiencing issues with set relation data. When im setting the document id from the related database most of them seem fine, except one table. ...
- REQUEST FAILED IN MIGRATION
I was trying to moved my archived project to a self-host database . Though the Project is "read only" but there's a message that I can view and migrate data to...
