Is this a bug?
I have a Goal on which I list 3 Tracking types - Completion Rate, Time Spent and Satisfaction Score. Each day 3 new Tracking rows with their daily values are inserted for this Goal.
Currently, there is a Goal Tracking table for entered daily Tracking type rows and the Goal Detail View is showing an Inline Table with all of the Goal Tracking entries - (in this example 21 rows - 3 row over 7 days)
In the Goal record, I ALSO want to be able to show an individual chart for each of these Tracking items.
In attempts to accomplish this, I created 3 Slices filtering ALL Goal Tracking rows by the Tracking Types. I then added 3 Virtual Columns to further filter these slices into lists for that Goal. The expression in these VC’s are similar to:
REF_ROWS("Completion Trackings", "Goal")
When I view each of the Slices data, they are shown properly filtered.
When I display the Virtual Column lists in the Goal Detail view, the counts in the inline tables reflect the correct expected number of rows - 7 rows per Tracking Type.
HOWEVER, the actual list displayed in these custom lists is all of the rows for that GOAL - i.e. the same 21 rows in the original Inline table - AND the View used is based on the base Goal Tracking Table not the Slices.
Inline View for Completion Rate Tracking rows
Tapping View Button - Original view and table - not based on Slice as the datasource?
Am I doing something wrong for my custom Virtual columns?
How do I get them to use System Inline Views or my own Views based on the Slices?
Solved! Go to Solution.
How do you have this field set for your new REF_ROWS VC?
Thank you!! Of course it’s something simple…I looked at this several times yesterday and I didn’t even notice that it was the base table and not the Slice. Thank you for pointing it out!!
Lesson learned - don’t watch NFL football and code at the same time!!!
Haha, that’s a good one.
BTW, It happends when you change the dataset of a REF_ROWS()
expression.
If it’s done from the first time pointing to the Slice, AppSheet editor takes the right dataset (table/slice). When you change it, you have to make sure to also do it down there
That’s why I hate system views and everything system-created.
Can you post here your column config as @Marc_Dillon said? I was about to point that out because I had problems with it in the past
Don’t think this way. We take for granted System views way more than you probably realize. Besides, in this case, it’s not the System views that were at fault.
When I created the custom Virtual Columns, I originally used my own SELECT statement on the base table. I then realized I needed Slices and can use REF_ROWS. I updated the columns but the base table did not change. I needed to do that manually. Doh!
I get it, they are powerful nonetheless.
I just have problems with system-created but it doesn’t apply in this case.
Happy you solved the problem!
User | Count |
---|---|
14 | |
11 | |
9 | |
7 | |
4 |