How appsheet determines the view type of a related column?

I have a table of customers and a measurement table containing several measurements of their body.
The tables are related using a Customer ID column.
So the Customers table has a “Related Measurements” column showing with the formula: REF_ROWS(“Measurements”, “Customer ID”).

I have created several ref views from the measurements table that I planned to use in separate views/dashboards.
One view is of table type and 4 others are chart type.

I want the Customer_Detail view to pick the table view when showing related measurements. But it’s picking one of the charts instead…
Can you please explain how Appsheet determines the view type to be chosen if there are several ref ones?
I even tried going to the chart one that was chosen by Appsheet and changed it to be table type. What happened is that another one of the remaining 3 charts was chosen!

Is Appsheet giving priority to ref chart view over ref table views?

I hope it was clear :slight_smile:

Thanks in advance

It’s been awhile since I looked into this myself. As I recall, it has to do with the order you added your ref views: likely the most recently added ref view is the one chosen. To “promote” an older view to newer status, copy the older one.

Thank you Steve for your reply.
Unfortunately, it doesn’t seem to work.
After some testing, my conclusion is that it seems it will always take the latest CHART over any TABLE view…
I actually went and deleted all charts and re-created them. didn’t help…
The latest view was a chart, so I even went and changed it to be of table type. The result? It took the chart that was created just before that one…
Is this expected behavior or a bug?

Thank you

I suspect the behavior is “undefined”, meaning there is no “expected” or “correct” behavior. I’ll look into it more, though.

So I think the question of how the app chooses a view is probably academic; the solution to your problem is likely the use of a different slice for each ref view.

1 Like

That’s seems to be the only way I have solved this… but it’s not really academic because it seems illogical and inefficient. I wish I understood the Appsheet design assumptions so it made sense how to approach app layout (less trial and error)…

1 Like

Here’s how the choice is currently made:

  • Ref views get higher priority than non-ref views
  • Explicitly created ref views get higher priority than system-generated views
  • If all else is equal, we choose gallery > chart > map > deck > table > card

Now that last part is questionable — we wanted to select more specialized presentations ahead of more generalized presentations.

We could have required that it be explicitly specified or at least go with a default that can be explicitly overridden. Still might be a reasonable thing to do. Adding @morgan FYI


@praveen - Thanks for sharing the logic! Love the idea of going with a default, but allowing us to explicitly override. Best of both worlds?

Doesn’t happen too often but when it does, this drives me crazy.

AppSheet creates a system generated deck view for map points but does not expose this deck view as it does with other system generated view. Defining a deck view (ref) will override defined table (ref) views.

Madness I tel you…

@praveen @morgan

I know how you feel :sweat_smile:
Please try to order the table view and the deck view to
first: table
second: deck
For example: If you have “My_View_Table” and “My_View_Deck” the deck will appear first and will “override” the table view. Just rename it like “My_View_Table” and “My_View_ZDeck” and you will be happy :grinning:

@praveen Any update on this?

1 Like

The workaround I described above doesn’t seem to work anymore. We seem to have no control over the Inline Views.
In a Gallery View, even when we set Show if to FALSE, it will be used as the Inline View.
The only workaround seems to be:


Yes I figured that out, but I think it is aukward. I think I rather just say in the detailed view which related view I want.

1 Like