Hi,
so I have a table called Software, which has a Title and a table called Category which has a Title too.
Each item of software, for example "Audacity" can have multiple categories "Audio, Cross Platform" etc.
On the Audio category screen, I'd like to reverse lookup all the Software items that have an Audio item in its Category column (note there can be more than one).
I've tried ...
FILTER("Software", [_THISROW][Title] [Category] ) ...and set the field type to List or EnumList... I've tried using IN, and SPLIT.
This is why for me, AppSheet REALLY SUCKS. Doing foreign_keys when there's only one item is easy peasy, it seems to handle that bit brilliantly, but connecting many-to-many fields in both directions is like the first use case for what any low code tool should do well, and yet I seem to be pushed towards creating fugly spreadsheet formulas (that I coulda done with actual fugly spreadsheet formulas) and the whole point of this tool it to make it easier.
I tested NoCoDB this week, and it handles this with flair.
Can anyone help me understand how to make my Category screen display a list of Software items have a given Category. I failed on this last time I tried AppSheet (watched lots of videos, read documentation etc) and still failed. And it looks like I'm about to stumble at the first hurdle again.
Tbh, these virtual tables could be created for me automatically - with all the horrible formulas, and type settings etc... or on a click of a button. It seems it'd be easier to delete them where I don't want them, rather than create them (by hand). It's a bloody common need... of any many-to-many joined tables isn't it?
Like I said, this thorny issue - a tool to handle many-to-many relationships easily is what any tool claiming to be better than a spreadsheet should do with elegant ease.
Thanks.
Solved! Go to Solution.
Oh sorry to know that the sample app is giving errors.
Sometimes the sample apps do not work as over a period time the creator may have moved some underlying table etc.
Here is another example of bridge table in the sample app below.
Order details is a bridge table between "Orders" and "Products" table. Each order can have many Products and each product can have many orders.
User | Count |
---|---|
16 | |
10 | |
9 | |
8 | |
3 |