Enhance CONTEXT() to allow access to Dashboard AND View properties at the same time

Currently, when a view is placed into a Dashboard, we can no longer access those view specific CONTEXT() details…they are obscured by the Dashboard View. In other words, when accessing CONTEXT(“View”) or CONTEXT(“ViewType”) within any of the “proper” views contained in a dashboard, we will instead be returned the dashboard details. This prevents us from doing things such applying Format Rules to one view and not another when both are against the same dataset.

I would like to propose that the CONTEXT() function segregate access to Dashboard details from all other views. This makes sense because a dashboard is really a container of views rather than a view itself.

I suggest that CONTEXT(“View”) or CONTEXT(“ViewType”) always refer to “proper” views whether they are included in a Dashboard or not. For any expressions operating in the context of the dashboard ONLY, these properties would return blank.

Additionally, introduce a new CONTEXT() property named “Dashboard” used as CONTEXT(“Dashboard”). This property would return blank if no dashboard is present. Otherwise, it returns the name of the Dashboard. This allows a single property to provide inclusion, view is in a dashboard, as well as Dashboard name details.

App Developers can then create context based rules concerning combinations of dashboards and views.

On second thought, this request probably will never happen as described, because it is not backwards-compatible. You’re suggesting changing how CONTEXT(“View”) works under dashboard cases. This would break apps that are already using the current way it works. Any new features like this really needs to just be adding completely separate functionality. A “better” request I think would be something like CONTEXT("ProperView"), which would return the actual View instead of the dashboard.

1 Like

Yeah your right. I suppose I shouldn’t be advocating HOW its implemented anyway, just that it’s needed.

1 Like

I think when they release the update for the detail views, the one that will allow us to create dashboard like views within a detail view, that will probably solve this problem.