1 of 1 people found this helpful
Hello Tom Sovich,
First off, welcome to the Tableau Community forum. Since this question is related to Tableau Server, I have moved this question to the Server area where a number of Tableau Server administrators assist other users.
Have you reviewed the User Filter capabilities of Tableau Server? here: http://kb.tableau.com/articles/knowledgebase/row-level-security-and-user-filters
Is there a capability missing with user filtering that is desired?
1 of 1 people found this helpful
Thanks for replying Patrick. The missing capability I'm looking for would be the ability to set the default value of a quick filter to USERNAME(). The second sentence of the link you provided says "Alternatively, you can create filters to limit the data that any given person can see". The keyword there is limit. I do not want to limit anything. All users need to be able to see all data, but I want to set the quick filter to recognize the user automatically and populate the value in the quick filter so they initially see their data. There is probably a way to accomplish this with a parameter but was hoping for a simpler solution.
2 of 2 people found this helpful
The closest thing I can think of to set a default value when going into the workbook is to set it on the URL line (if the user is using a URL to get to a published workbook.)
Keep in mind that this is not a URL string, so unlss you are sending the user somewhere from Tableau to this URL, you don't have the USERNAME() function avaliable to you. You'll have to get that value somewhere else. (Maybe each user will have his own URL bookmarked, or an icon on his desktop, etc.)
This format will place the user on that dashboard with that filter set to the specified value. (BTW, you can do the same with parameters.) The rest of the filter will still be there for him to select from. It just starts off preset to the specified value.
3 of 3 people found this helpful
I know this is a late response, but since I got here by googling this problem I figured I might add in how we solved it.
We had a very similar use case (multiple users, want to show the user his own data by default but still able to select data of others). The workaround that we are using is by adding an extra user "default", publishing the workbook with that value selected and doing the actual filter on a calculated field along the lines of:
IF selected_user = "default" then username() ELSE selected_user
It's not as clean as having actual default values per user, but it does the trick for now.
Good morning. Is there any way you could attach a workbook that shows how you implemented the workaround above?
We are dealing with this exact situation where I work. Our data source is MS SQL Server, so I wonder if upon seeing your solution, we could modify it (if need be) and try it on our end.
4 of 4 people found this helpful
Karl-Henry Cesar - I don't have a simplified workbook that I can share publicly, the ones I have contain company sensitive information that I can't share. But explaining the basic steps we took below.
Toby Erkson : No, we didn't create a dummy user, apologies if my description above is ambiguous. I started from our dataset, which was a list of sales contracts. Created a parameter called "selected_user" which took all possible values from the "contract_created_by" field of the dataset (which is in theory independent from the active directory users but in practice contains the same possible values), plus one extra value that I manually added called "default". This parameter is what is exposed to the user rather than the actual filter.
Then I added a calculated field called calculated_user with the formula IF selected_user = "default" THEN USERNAME() ELSE selected_user END . Then the actual filtering is done on a 2nd calculated field, a boolean with the calculated_user = contract_created_by, which is filtered on TRUE but not visible to the user.
There may be simpler ways of achieving this, but it's what we came up with.
Mark -- That'show I envisioned the solution you suggested back in October. Makes sense.
I squirreled that idea away in my bag of tricks for future use.
I need a similar capability. Default a user to a subset of data but still allow them to see the top level aggregation if they choose to modify the filters.
Is this still not resolved yet? I can't believe such a basic requirement is not available. I need to have a default value for a date filter, so the date selected is always the latest date. Right now the users have to change the date filter every time the data is refreshed. I can create a Boolean filter for is latest date and set that to true, but then I have to explain to users if they want to change the date they have to unselect that and then change the date. It's embarrassing to have to explain to users workarounds for such a basic filter with a tool that is supposed to be one of the leaders in the data visualization arena. In the end our users are not adopting the tool, because as soon as you start explaining a workaround you lose them, and we continue to use reporting services for most of our reporting needs. Hope this get's resolved soon.
I completely agree with @Eric_Hanson that this should be an obvious requirement for any product being deployed at the server level. Explaining a work around to users isn't an option, the tool has to be intuitive enough that they can figure it out without having to think about it. Please add features to customize the defaulted filters by the username, parameter, or max/min.
We're not looking for user filters or row-level security here. The status of this request should not be "Assumed Answered"
Mark's solution works and is an acceptable, simple answer to solving the question at hand.
If end users are unable to accept the fact that software can't be perfectly everything to everyone (because I've yet to see a business application that is 100% flawless) then they are in the wrong industry. In fact, the wrong mindset!
Is this annoying? Yes it is, I agree. Vote up the Ideas that kettan has posted above.
If you're connecting to SSAS this isn't an acceptable solution because of it's limitation to create calculated columns off of dimensions. Unfortunately, we don't have the same flexibility for workarounds. We are hoping Tableau takes this up as an enhancement so I'm bringing as much attention to it as possible. It's not a show stopper and adding certain filter to context helps, but it would be a huge help to have more customization around what defaults when we post our dashboards.
When a user selects a worksheet on Tableau Server they're able to set up "Custom Views". Sure it's not dynamic and it puts the burden on the user base, but it's a better option then having them reset all the filters to see their data. This might not be a solution to everyone looking for dynamic filters, but maybe to some.