Let end users show and hide filters and more with this extension | What's new Tableau 2022.3 

Thank you so much for your work and feedback! I’m an experienced Tableau developer, and when I discovered your channel I was so happy, finally an answer to all my questions! I just watch your video for fun before going to bed, they are so light and well made and on top of this also mega useful 👍👍👍

Love this new extension! We discovered it with a client a few weeks ago, and it was a game-changer for us. A good thing to know is that if you save a Custom View, it also remembers the user selection within the Extensions. The same dashboard can display different filters for different people according to their Custom View. Hope it makes sense :) Great video, as always!

Great video. For me I often have to add lots of filters to try and cover many scenarios. Using this I'll be able to add lots of filters to the view, then hide them and let the user choose which ones they wish to show. And as for whether it does what it's supposed to, I think it does that, plus more, which is a bonus it works on tiles, titles etc as well as filters.

This extension is helpful for me on two fronts: 1) many stakeholders require many different filters and they can't all be present at once (not enough space), and 2) it is an opportunity to enhance the data literacy of our workforce because those who have the time can self-serve their own data but will require a little bit of training which has a trickle down effect to their clients. For dashboards that enable more analysis, this is a great feature to make a sandwich board where two identical dashboards can be arranged side by side allowing a side-by-side comparison of data - for example, to compare two similar business portfolios at the same time. That being said, the only elements I include in this extension are filters and potentially some specific containers. We still need to keep the UX as easy as possible. Thank you sir!

Great video! My main takeaway was about extensions. Thanks for sharing the detail about sandboxing! Wasn't aware of that. Can't think of a use case with this extension. It'll be interesting to see if adding filters not already in the view becomes available in a future versions. I think the marketing got ahead of what the feature actually does.

A quick FYI for anyone who is working with the add filters extension. If your filters are in a container which already has a show/hide button, then show action when you click the button for the container seems to override the hide option of the extension. Long story short, it seems like this extension only works if your filters are not in a container that also has a show/hide button.

Thanks Tim. I love that you do the research for those that don't have the time. I wholeheartedly agree with your point regarding the extension being the wrong way round and so not what it advertises. I have been waiting for this feature and, like you, overlooked it on release. Now that I've used it, I'm very disappointed. I develop dashboards for other stakeholders and must make them as self-supporting as possible as I don't have the resource to train, maintain and support each custom requirement. Consequently, this feature is of no use to me as I must include every single filter or item that a user may want to switch off. I would then have to be available to respond to every single individual query on how it works, what the optimal configuration is and every other conceivable question on its use. I already model with a user 'config' dashboard which allows my colleague developers, or users, to make session changes as required using parameters, filters and set selections; some users will also go as far as save a custom config. What I am really in need of is a means to provide a user the ability to add or change the original, focused, dashboard to meet their specific filtering needs, not remove and save it specifically for themselves. Such features will confuse or annoy many users who expect a dashboard to first do what it was designed to do with an option to customise if required, in only a handful of cases. It really is as though Tableau had a 50/50 choice in which way to go on this and got it wrong. Think how powerful this feature (done right) would be with dynamic zones; one could build a SINGLE model but have various configurations for different market sectors such as restaurants, offices and retail customers who all have the same lease management requirements but different filtering categories. I do wonder how hard it would be to reverse the feature to first ADD filters which have been pre-defined by the BI developer for such use. Coincidentally, I had a similar problem with another BI platform a few years ago which, through direct engagement with the developer. resulted in this feature being developed and successful deployed so it is possible. Again, thanks Tim, You have helped me so much

Hi does the extensions transfer data to any third party element?i mean is it safe to use extensions on client secure data data.? is it advisable to use them when data security is a concern?

Very interesting 😀

Can we configure 'Show as Tabs'. I have a tableau file with 5 dashboards. I want only 3 of them to be displayed as tabs when published in server. I want the remaining 2 as a drill through which we can set using actions, but needs to be hidden by default. If I hide that while publishing, it will not allow to perform Actions to that dashboard. So I need a way to set only desired dashboards as tabs and others not as tabs. Is that possible?

I worry they would say, something is wrong! It won't run or something like that.