Separating format rules between 2 views of same table within dashboard, not possible right?

[Marc_Dillon]

I have a dashboard View which contains 2 different table Views, but they are of the same Table. I was hoping to have a format rule affect a column’s value in one sub-View, but not the other.

Pretty sure this isn’t possible, because CONTEXT() would just return the dashboard itself. Just wanting someone to confirm if they also think it is impossible, or maybe if there is a way? Besides duplicating the column.

Thanks

[Koichi_Tsuji]

Yes, I agree this is impossible for the moment. One of the AppSheet existing capability and limit.

If we could get Context(Slice) to return the name of slice is introduced, then possibly we could make this happen by creating each view element inside dashboard to be generated by table and slice though.

[WillowMobileSys]

@Marc_Dillon

I too agree this is impossible.

Wondering what other thoughts are? I have wondered about CONTEXT() with Dashboards for a while now. It’s obvious that we need to be able query for Dashboard details as well as details for the child views.

In my opinion, “View” and “ViewType” should continue referring to the views whether they are in a Dashboard or not. We need different properties in CONTEXT() for Dashboards, because well, they are entirely different.

For instance, maybe CONTEXT(“Dashboard”) that returns BLANK if the view is not in a Dashboard or the name of the Dashboard. A single function that provides both inclusion and name information.

Another option is discrete functions:

• CONTEXT(“Dashboard”) that returns TRUE/FALSE for inclusion
• CONTEXT(“DashboardName”) that returns, obviously, the name of the Dashboard that the instance of the view is contained in.

Should a feature request be submitted to enhance the CONTEXT() function?

[Marc_Dillon]

WillowMobileSystems:

For instance, maybe CONTEXT(“Dashboard”) that returns BLANK if the view is not in a Dashboard or the name of the Dashboard. A single function that provides both inclusion and name information.

WillowMobileSystems:

Another option is discrete functions:

• CONTEXT(“Dashboard”) that returns TRUE/FALSE for inclusion
• CONTEXT(“DashboardName”) that returns, obviously, the name of the Dashboard that the instance of the view is contained in.

Doesn’t seem necessary to me.

WillowMobileSystems:

Should a feature request be submitted to enhance the CONTEXT() function?

Probably.

[MiguelPilo]

This problem is still impossible to solve? Or during this time has been any solution?

I'm according with the option that CONTEXT(VIEW) affect into dashboards

[Trevwiller]

Create two slices that are from the same data that you want to display. Create a view for each slice. They Both will display the same data, but now can have format rules applied separately. Now put the two views referenced into the dashboard view

[MiguelPilo]

Thats exactly what I did. But, format rule it's only available in the context of the specificed view due CONTEXT(VIEW)="ViewName" and when is included in a dashboard the rule is broken because now we have CONTEXT(VIEW)="DashboardName". And if we use the format rule with "DashboardName" the rule will be aplied for all slices not just for the specific that i want to.

[jaichith]

So you mean that rules are not applicable for REF type views ? 

[MiguelPilo]

Not. I mean that CONTEXT(VIEW) rules apply for the main view, and in a dashboard, the main it's the "DashboardName" so, the views into the dashboard do not use the rule directly, these use it through "DashboardName", because of that, rule apply to all views not just the specific one required.

[JMPeterson]

Could you turn your slice conditions into a TRUE/FALSE virtual column, and then apply the format rule based on that virtual column result? 

[MiguelPilo]

Thanks JM.
That's an feasible solution. Not the optimal one because requires duplicate data, but definitely solves the problem.