I’m sure that everyone does something very similar, but I have a [User] property in nearly all of my Collections in order to keep everything in order so that a user can access “their” data. When I began building my app, I would create a One to Many relationship and when I would simulate a user creating a record, I could see that user in the [User] property within that Collection.
For some reason, that stopped working. It appears that the records are still connected to the given user, but it is no longer showing up within the Collection.
My workaround was to create a [User ID] property where I manually collect that information and associate all of my lists and such using that Property instead of the native relationship.
Has anyone else experience this issue and what did you do to solve it?
Hey @ThunderBlade, could you please share an image regarding this issue?
The User relationship in collections can sometimes stop displaying correctly in the editor view, even though the relationship itself is still working. It’s a display issue in the builder, not a data issue.
Your User ID workaround is actually a good approach and many experienced builders use it intentionally. That said, it’s better to check a few things if you want to restore the main relationship display:
First, try refreshing your browser completely and clearing the cache, sometimes the collection viewer just needs a reset to show relationship data correctly.
Second, check if the relationship still exists properly in your collection properties list.
Third, if the relationship is available but still won’t display, duplicating the screen or the list component and rebuilding it sometimes makes the relationship to display properly.
Your workaround works, but if the relationship is still connected, your lists will perform better navigating through the relationship chain than filtering by User ID.
Ali Bazzi — Adalo Expert | adalo.com/experts/ali-bazzi