Please take a look at this sample application. What I did here was to load my main table (Fruits). Then create two separate identical tables from it in the load script. This way I could then have two identical, but disjoint list boxes of all fruits. Here the user can pick a fruit (or group of fruits) from each one of these two list boxes and the table to the right will compare the average count of the selected fruits from each list box.
My question is this. Can one accomplish this functionality without creating two copies of the original table. My real table has millions of rows and this is not an optimum solution.
Yes, I tried that but the problem is this syntax cuts off all other selections from other fields in the app. What I need is to include the alternate state selection plus all other selections in the app minus the third inherited Fruit list box. So I tried the following syntax:
{$*A <Fruit=>}
assuming it accomplishes the above, but it seems like it completely ignores the {A} state and only takes the inherited Fruit list box
So in the modified attached app, if peach is selected from Fruit A box, selecting stores S1 or S3 should not change the Group A value since peach selected in Fruit A belongs to both stores- it should return 8. And if the user selects the S2 store it should not return anything since peach does not belong to that store.
