How can I hide a card, filter, or custom control on a dashboard?

D_Markley34

We have a business case that requires us to have a control that sets a variable that we use to determine which column to display as part of a visualization. The value of the control will be preset. We want the control to be hidden on the dashboard. How can this be accomplished?

Ashleigh

@D_Markley34 could you add the control directly to the card instead of the dashboard? What is the reasoning for using a variable here. Usually variables are used so people can change the values being shown, otherwise you can just hardcode the value in without needing a variable.

marcel_luthi

If you're determining what will be shown based on the user, an alternative might be to use one of the values in domo.env rather than a variable, and limit the shown columns based on this. You could extend this if you also have a dataset from the Domo Governance Datasets. Just mentioning this as a possible alternative so you don't have to deal with the variable, setting it and all that.

Ashleigh

@D_Markley34 ah that makes more sense, this sounds like it would be a perfect use case for Column Masking once that becomes available.

Ashleigh

@D_Markley34 could you add the control directly to the card instead of the dashboard? What is the reasoning for using a variable here. Usually variables are used so people can change the values being shown, otherwise you can just hardcode the value in without needing a variable.

D_Markley34

In reading my original question I failed to mention the custom control is in a data brick making it necessary to have it on the dashboard. We have one set of users that can see an employees name and another set that is only allowed to see an employee ID. We have created a custom control in a data brick that allows us to pass the info we need to automatically set a variable that we use to control the column to display.

marcel_luthi

If you're determining what will be shown based on the user, an alternative might be to use one of the values in domo.env rather than a variable, and limit the shown columns based on this. You could extend this if you also have a dataset from the Domo Governance Datasets. Just mentioning this as a possible alternative so you don't have to deal with the variable, setting it and all that.

Ashleigh

@D_Markley34 ah that makes more sense, this sounds like it would be a perfect use case for Column Masking once that becomes available.