That’s a nice idea–although, ideally it would be a column property not a universal app property.
This is also a problem with the labels used in grouping in aggregate views, and with column display names.
Yep! Just try to make a Table View including a column with a Display Name that has an expression @dbaum
Right. The way I’ve found around that is:
IF(CONTEXT("ViewType") = "Table", "default column display name", "row-specific column display name")
For custom true/false values, using CONTEXT doesn’t affect pie chart labels–apparently, any expressions in those column properties are not even referenced in the first place when AppSheet determines chart labels.
And what is shown now using the Desktop preview where CONTEXT() misbehave? Just curious as my “View” button on inline views is messed up
Good question. I haven’t taken time yet to explore the new Desktop view functionality.
I wonder whether evermore frequent status notifications mean anything… Here’s today’s.
AppSheet Support
Hi, this is to inform you that it needs more time to fix the issue.
Thanks for your understanding!
Just be glad someone is actually looking at the ticket and it hasn’t been abandoned. That said, I would imagine this bug is a low priority.
Keep it up!
FWIW, status notifications are now reliably every 3 business days. Today’s message:
AppSheet Support
Hi, this is to inform you that it needs more time to fix the issue.
Thanks for your understanding!
Noticed the following in the September 15, 2022 Release Notes.
Bug fixes
| Item | Description |
|---|---|
| Bug | Custom Yes/No labels are now supported in chart views. |
Indeed it’s now working.
Column does not have custom values: Chart labels are Y/N
Column has custom values: Chart labels are the custom values:
FWIW, here’s the behavior when the custom value varies across rows.
Custom false expression:
IF(MOD([_RowNumber], 2) = 0, "Even", "Odd")
Data:
It’s unclear how AppSheet determines which of multiple custom false values to use as the chart label. Regardless, as we’ve discussed in this thread, that’s an edge case with no self-evident way that it should be handled within current AppSheet functionality and is perhaps consistent with analogous scenarios like column header labels in table views.
Good to know these updates. Thank you @dbaum
And another entry today in this case study in AppSheet support…
AppSheet Support
Hi, this is to inform you that we need some more time to fix the issue.
Thanks for your understanding!
Me
AppSheet release notes from September 15, 2022 indicate this bug was fixed, and it looks to be addressed for the main use cases. See screenshots in the community post on this topic. Are further improvements still planned?
And, maybe the final entry
AppSheet Support
yes, it was fixed, it just should have rolled out around a week or so.
So, thanks for the confirmation!
Ugh. Support is a disaster.