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
- Weird permission failure
when creating an account I use following methods: ``` Future<void> register(String email, String password, String username) async { final user = await accoun...
- Relation Question
How do I create a relation from table y to an others x.$id. in my example I have a users table where I use Appwrites unique User IDs and I want other tables fo...
- Unknown attribute type: varchar / text
Since the `string` type is deprecated I tried using `varchar` and `text` in some newer tables, but when running `appwrite pull tables && appwrite types ./src/li...