Trialling Softr Databases with a view to replacing Airtable and like the uncluttered UX. However, at present I can’t see how we can implement the following use case example (essential for us and I expect many other users):
We have a table of Users and a table of Accounts. Each user can belong to multiple accounts; each account can have multiple users.
Where a user-account relationship exists, we create a record in a junction table ‘Memberships’ which links to the user and account in question. That record also holds information on the specific permissions and other settings that apply to the user with respect to that account.
In Airtable, we then use conditional look-ups to eg list the account(s) for which a user has an active membership.
I understand - but correct me if I’m wrong - that the implementation of ‘related records’ and the various requirements for supporting relationships are still at an early stage in Softr DB. Has anyone explored this issue and come up with any workarounds? I may have missed this in the roadmap, but my search didn’t yield any results. NB I’m not a data scientist (although I have a good understanding of the principles) so forgive me if I’m missing something.