We use custom views extensively. One way is to allow different users to filter a report to just show the data for their "region" (in our case, the machines they are responsible for). Those are private views. Another way is to allow a user to save an exclusion list of data that should not be considered in the averages discussed at our weekly meeting. That is a shared view. We've really noticed when these custom views have been broken by various versions of Server (see multiple threads in this forum). Our only feature request would be to allow users to save an unlimited number of named custom views, any of which could be shared.
Hi - we have the same use. The various managers filter explicitly to their regions and then can have it as a favourite or default tab in the browser.
I too second the addition of the ability to save multiple custom views. That way we can use the same published workbook for regional management and individual management (with exclusions for secondments and whatnot).
At the moment we are not using this feature extensively due too the fact that only one view can be saved per user. Having the ability to save multiple views per users would add a lot of value for us as we mostly use very generic workbooks that have to be parametrized by the user.
Thanks for the feedback Zach, Nathaniel and Peter. Yes, the ability to have multiple customized views is something that we are working to support after 7.0 ships. One thing that would be good to understand is whether you have a need for 'private' saved views. What I mean by this is the following:
Today, you have 2 options when saving a view, 1) either it's private and ONLY visible by the user or 2) it's shared and is visible by everyone and seen in the list of customized views available.
What we are thinking about is to replace the first option with a view that could be accessible by others but not shared in the global list of shared views. So, I could create my set of filters then copy the URL and send it to someone else via email. Of course, the recipient would need to have permissions to access the workbook and data in the first place.
What do you think? Do you think that there needs to be a 'private' set of custom views? or is the idea of a personal view that can be shared acceptable?
Thanks in advance for the input.
I think being able to globally share any or all personal views is adequate. If you change personal views to allow URL sharing, users will have to remember whether they've given out the private URL to know whether or not it has been shared.
As for the saving and sharing interface, consider adding a Save As... option below Save to save a custom named view, and consider displaying the list of globally shared views to include or cascade under the saver's name, to prevent naming conflicts between users, and also let viewers know whose view they are looking at.
I think it is a great idea.
We don't use personal views much because there is only one slot for it, and there is no way to give it a meaningful name. Allowing more slots will make things worse, because users will have to wade through countless custom views added by other users to find their own.
It would be better to be able to add multiple private custom views, only visible to the user, but be able to share them with others via URLs. It is important to be able to name those custom views.
I think Xcelsius had something similar with scenarios, and Excel has a primitive version of this.
I personally can't see much value in the second option, unless it can be annotated and directed at specific users, but that would be same as the proposed first option.
Yeah, I think you're right Dimitri. The way Sharepoint does it (with a slight tweak) would work well I think:
- multiple views
- views can be named
- views can be made public or kept private (but being able to send a URL would be good)
- I think extending it to be able to use the Server users and groups would be useful (but needs to be kept simple to do)
I disagree with Dmitri's comment that allowing more slots for globally shared custom views will make things worse. We currently trust users to only make their single custom view public if they have something interesting to share with everyone. If we allow multiple saved views per user we can still have users select which ones of those to globally share.
On the release notes for Tableau 7.0.2, one of the enhancements is:
"Added the ability to create multiple customized versions of a view that can be shared, or "advertised," to other users. You can customize views while browsing Tableau Server or while interacting with an embedded view.You can also embed a custom view."
Does this adress the comments in this post?
Any documentation or examples on how the new feature works?
This is awsome!!
Does it also works on the Ipad App?
Glad you like it. Yes it does work on the iPad. And it works in embedded mode as well.
Remember my changes is a nice feature but we would like to have a way to disable it (hide the capability), because we don't need it .
Could you add an option like 'tabadmin set vizqlserver.showRemember false' or a user permission "Remember Customized"?
I would like to mention also that the Advertise option is nice but we can't use it as it is today.
For example we have two Clients A & B that access the same tableau view, client A and client B see only their own data
Client A has two tableau users (ClientA1 & ClientA2)
Client B has one tableau user (ClientB1)
ClientA1 save a custom view "Client A financial reports" and advertise it in order to show his analysis to ClientA2.
ClientA2 will see the custom view "Client A financial reports" and get the data when accessing the tableau view. That's good.
What's not good is that ClientB1 will be able to access "Client A financial reports" without the same data. This is not acceptable for us to allow a client to see other clients name.
I would appreciate your comments about it.