How to display selected filter values on dashboard

A common request we get is to prominently show in the dashboard header which values have been selected in a filter.


I am wondering what is the easiest way to accomplish this - namely, how to show the value exactly as it appears in a filter in a label component. Currently we need to create a custom script and attach to the parameter value changed action and make sure it matches up with the filter attributes - the type, tokens, parameter values, etc. - which is cumbersome and requires a different script every time.


Is there an easier way to do this? I just want whatever is selected in the filter to show up in a label, regardless of what kind of filter it is or which token is selected.

Is there aw ayou can show us a picture of what you are currently doing? I think I have a picture from what you have said but not sure if these are single select or multi selections (are you just using the right click filter or is there one there).


If it is multi selectable how do you plan on fitting all the possible selections in the label area? Currently with a filter selection on the screen it shows you what has been selected but fills up real fast when you select more than one option. So this would work as a solution to just have an actual filter but only for one item being selected.


I think this will need to become a Feature Request. I woudl not be to difficult to make for single selections but when you can have multiple one and a very long list selected I am not sure it woudl be practicle to try to show them in a lable. A toop tip would be better for that. other wise you would have to make a label big enough to show the top ten in the filter and then by what order do you want? and when it is just a token selected the space is wasted.

In this example it is a multi select filter with a hierarchy. The script is attached to the Parameter Value Changed action on the filter component. If a token is used, then the unresolved token value is displayed. If multiple items are selected, then all items are displayed. Fitting multiple items in the label is handled by 1) leaving ample real estate for the label component, and 2) the script looking at the resultant length of the label string and reducing the font size accordingly.


I agree the label is redundant and wasted space but this is what our users seem to unanimously want. The problem is that the script needs to be so complex just to get the label to show the same thing as the filter - the script needs to define every possible filter selection with if/else statements, iterate through the selected filter values with value.uniqueName.split, and output a string to ultimately display in the label. What I don't understand is why it needs to be any more complicated than labelExample.labelText = viewParameterExample.parameterValue.[TheExactSameCaptionThatDisplaysInTheFilter]



If that is what my users demanded and I had to do it I think I woudl have done it the same way and wondered the same question of why so complicated. If I was to take a guess as to why, they never thought some one woudl do this so the API does not have an easy way to get it. But I give them a B+ for it being able to be done at all, even though you jumping through a lot a hoops to get it done.


I say just change this over to a feature request to make something liek this easier at least in the API calls that makes it happen.


But lets also wait and see what they say and suggest.

Hey Dave,


Depending on the length of your list of filter values (if it's not too long / doesn't require scrolling or multiple levels), you could consider using a checkbox list as a filter. This way, all of your filter values are always visible.


This is how it may look:



that being said, I assume your filters has many values and/or multiple levels. In this case, using a scripted label is the best option at the moment.


We have an open Feature Request (#68336) to accomplish this without scripting, and have added you as a requestor.


1 Like

I can see why users want to see this with out having to open the filter control.

Personally I would only use it on a dashboard that is shown on a big screen that every one looks at and maybe with a script to change the filter on a timer.

Also depends on what the users want, they are the ones signing our pay checks (so to speak).


Thanks Jordan for adding me to the feature request. This is a multi level hierarchy with a bunch of items so anchoring the whole list on the page won't work. Essentially the requirement is to make filter selections more visible to users. Rather than duplicating the filter selection in a data label, this could probably be accomplished simply with better control over the filter appearance properties. Like being able to change the background colour, or hide that filter type icon. For some reason it seems like text size is the only property that doesn't get applied to the filter values, only to the label text.


More styling properties for filter controls (including the ability to change the background colour or hide the filter icon) are currently in development (Feature request #49585) and will be part of an upcoming release.

Brilliant! - can't wait