Chained dereference expressions for LIST TYPE

Is it possible to Chain Dereference LIST TYPE Columns. I have 3 tables

Table1(Parent of Table2)

Table2 (Parent of Table3)

Table3

Is it possible to Dereference the Related Column from Table1 to Table3 i.e something like

[Related Table2][Related Table3][Table3 column]

Solved Solved
1 13 673
1 ACCEPTED SOLUTION

@jyothis_m 

 I think one option can be  that you may need an intermediate column in the parent table ( Table 2 in your case)

In table 2 , you could have a VC called say [Table3_Column3_List] with an expression something like [Related Table3][Table3 column]

Then in the grandparent Table 1, the expression could be [Related Table2][Table3_Column3_List]

View solution in original post

13 REPLIES 13

Yes, with [RefColumnInTableA].[RefColumnInTableB].[ColumnInTableC]

@AleksiAlkio looks like he is asking List Ref top to bottom in the reference hierarchy. I tried the example you provided. Do you have any working example ? If this actually works then it would be nice. 

This works on 1st level but not on 2nd and 3rd levels

Screenshot 2023-08-02 at 3.49.48 PM.png

Not working on 2nd level 

Screenshot 2023-08-02 at 3.45.05 PM.png

Thank you @Rifad ๐Ÿ˜Š i can't explain any better ๐Ÿ˜ƒ

The chained deference has different meaning that is bottom to top hierarchy referencing using dots.

Dereference expressions - AppSheet Help 

Sorry I was confused.

Thank you for the reply @AleksiAlkio But, all these columns are of LIST type so the dot operator is not working since its a list dereference. I am able to dereference the first level i.e. [Related Table2][Related Table3] but when i try [Related Table2][Related Table3][Table3 column], its throwing error

Aaa.. I thought you were meaning the opposite, my mistake. With lists, not possible, unfortunately. Or at least I haven't found the way to do it directly without SELECT expression ๐Ÿ™‚

Sorry for the confusion. I have also finally used the SELECT expression. It would nice to have such a feature right?

Yes, I can see the benefit.

@jyothis_m 

 I think one option can be  that you may need an intermediate column in the parent table ( Table 2 in your case)

In table 2 , you could have a VC called say [Table3_Column3_List] with an expression something like [Related Table3][Table3 column]

Then in the grandparent Table 1, the expression could be [Related Table2][Table3_Column3_List]

Good workaround Suvrutt 

Thank you Aleksi and Jyothis. ๐Ÿ‘

That's a great workaround. Thank you ๐Ÿ˜Š @Suvrutt_Gurjar 

Top Labels in this Space