So, B has two ref columns, to A and C?
That means A should have an auto-generated virtual column called âRelated Bsâ, this is a list of B records refâd to A. So to get a list of C records refâd by that list of B records, youâd use:
[Related Bs][refC]
Where ârefCâ is the column name in table B that is the ref column to C.
List is only allowed for lists constructed directly from list-producing functions (e.g., REF_ROWS(), SELECT(), FILTER()) in columns that are not user-modifiable, if I recall correctly. For all intents and purposes, EnumList is equivalent to List, so thereâs no problem using EnumList. I have no idea why AppSheet has this distinction.
I would like the user to see the list C records when viewing a record A and click on individual record C to access its details. Obviously itâs what List of ref offers but if I canât do that, is there an alternative?
Was thinking of another solution.
Context: Table A and C has no linkage. Table B is a mapping table between A and C.
Letâs say I create an Enumlist ref of C in Table A. What would be the best way to display ref of C under a record A?
I think the general strategy for such a situation is that any fields in C that youâre wanting to see from the context of A, you should create de-ref columns for in B.
A fairly typical example of a many-to-many relationship is:
Orders â Line Items â Products
Where you create an order, and add line-item records corresponding to instances of products from a database. Obviously youâd want a list of products in your order, so you include a column in Line Items that de-references the display name from Products.
Unfortunately it doesnât seem like it is currently possible to build a ref list like how youâre wanting. So the question is, what function exactly are you looking for, and can we build it another way?
Table A contains Classes
Table C contains Activities
I made a dashboard that allows admin to build kid classes. First tab is Table A, second tab is Table C. When browsing Table C, the user can add Activities in the class via an inline action (+). I have a table B that have records created via this action.
Tomorrow, I am thinking getting rid of this Table B to simply have an EnumList Ref of Table B in Table A. Iâm anticipating generating class with random activities and thought it would be easier to deal with a list in Table A rather than generating a bunch or records of Table B.