Dashboard (ref) View Showif

I have a dashboard that starts with a primary detail view (of a row of data) on the left and other stuff (a map, etc) on the right. I am wanting to "open up" (ie, show) a secondary detail view (of the same data/row) if a toggle is selected in the primary view (both of these are obviously reference views since they are children to a dashboard). While I can clearly read where the Showif states: This formula is not evaluated in the context of a row, so column values are not available and thus it sounds like what I want to do is not possible, or at least, not in this simplistic form I am looking for (just a dashboard- no Actions needed).

Just thought I'd ask here if anyone knows a way around this limitation -that is, not being able to read a column value to determine applicability to Showif for a view?

Solved Solved
0 14 291
  • UX
3 ACCEPTED SOLUTIONS

ANY(ActiveUser[Show secondary view?])

View solution in original post

Hi @jharkless ,

I am elaborating Steve's solution, mainly because of time zone difference, understanding Steve may not be probably logged in to the community at this hour.

Please

1. Add a real column of Y/N type called say [Show_Additional_Details] in the Users table.

2.  add an action of type "Set values of some columns in this row" in teh Users table. The actions sets the column [Show_Additional_Details] with an expression something like 

 IFS([Show_Additional_Details], FALSE,
NOT([Show_Additional_Details]), TRUE )

3. Add this action as an inline action in the detail view of the ActiveIUser. This is the detail view that you wish to always display in the dashboard.

4. In the Show_if setting of the detail view that you wish to conditionally hide or show in teh dashboard, please add an expression something like 

ANY(ActiveUser[Show_Additional_Details])

Steve recommended use of ANY() because the expression  Current_User[Show_Additional_Details] technically produces a list, even though it will always contain a single value for the current user slice. Also note that since the "ActiveUser" slice is based on the email of the active user, once can specifically select a row of  the active user, unlike other columns that can not be used in show_if of a view because then the expressions become row based and row based expressions are not allowed in view show_ifs..

Hope this helps

View solution in original post


@Suvrutt_Gurjar wrote:

note that since the "ActiveUser" slice is based on the email of the active user, once can specifically select a row of  the active user, unlike other columns that can not be used in show_if of a view


This is not only an answer, but precisely the one I was hoping to find!

 

View solution in original post

14 REPLIES 14

How do you open this dashboard view.. like from where? Or..do you have only one record in that table?

The dashboard is the starting/main/home tab

Steve
Platinum 5
Platinum 5

If the "primary detail view" is always of a specific row, you can use LOOKUP() to get column values of that row.

It's the ActiveUser slice. And that's also my same intent for the secondary detail view as well. I'm really just trying to get a more control (ie, appealing layout) in my dashboard.

ANY(ActiveUser[Show secondary view?])


@Steve wrote:

ANY(ActiveUser[Show secondary view?])


The following is just a visual representation of Steve's solution.

Split_Detail-View.gif

 

Uggg, please excuse my ignorance (as a learning-on-the-fly newbie here). I don't understand the use of @Steve's response in the Show if constraint on a View, which is looking for a Yes/No evaluation- how does ANY() produce that?

@Suvrutt_Gurjar is what you are illustrating with your click on "Show Part Two" just a toggle or an action which you created for this purpose?

Hi @jharkless ,

I am elaborating Steve's solution, mainly because of time zone difference, understanding Steve may not be probably logged in to the community at this hour.

Please

1. Add a real column of Y/N type called say [Show_Additional_Details] in the Users table.

2.  add an action of type "Set values of some columns in this row" in teh Users table. The actions sets the column [Show_Additional_Details] with an expression something like 

 IFS([Show_Additional_Details], FALSE,
NOT([Show_Additional_Details]), TRUE )

3. Add this action as an inline action in the detail view of the ActiveIUser. This is the detail view that you wish to always display in the dashboard.

4. In the Show_if setting of the detail view that you wish to conditionally hide or show in teh dashboard, please add an expression something like 

ANY(ActiveUser[Show_Additional_Details])

Steve recommended use of ANY() because the expression  Current_User[Show_Additional_Details] technically produces a list, even though it will always contain a single value for the current user slice. Also note that since the "ActiveUser" slice is based on the email of the active user, once can specifically select a row of  the active user, unlike other columns that can not be used in show_if of a view because then the expressions become row based and row based expressions are not allowed in view show_ifs..

Hope this helps

That helped tremendously! I was actually pretty close but was missing that its the Slice itself I am calling with the ANY.

I was able to take this 1 step further and get what I wanted originally (which I wanted to wait to ask until I figured out I could get close) and that is to make it work with a multiple a choice (Enum) by leveraging IN() and looking for the choice that I want to trigger the 2nd menu 


@Suvrutt_Gurjar wrote:

note that since the "ActiveUser" slice is based on the email of the active user, once can specifically select a row of  the active user, unlike other columns that can not be used in show_if of a view


This is not only an answer, but precisely the one I was hoping to find!

 

You are welcome. I also wanted to correct my earlier a bit extended elaboration. Actually in this set up one does not need an action.  The toggle can be simply achieved with a Y/N type column set up as quick edit column in the permanent detail view instead of needing an action. The quick edit in detail view effectively works as an action. 

The demonstrating GIF below.Split_Detail_View_2.gif

 

Yes. An Action was not what I was looking for and being able to leverage a Yes/No or an Enum option is perfect. Thanks again.


@jharkless wrote:

was able to take this 1 step further and get what I wanted originally (which I wanted to wait to ask until I figured out I could get close) and that is to make it work with a multiple a choice (Enum) by leveraging IN() and looking for the choice that I want to trigger the 2nd menu 


Great. Excellent. You can have the enum simply as a quick edit column in the permanent detail view to expand the hide/show detail views to several detail or other columns.

 

Thank you for stepping in here, @Suvrutt_Gurjar! Excellent followup!

Top Labels in this Space