8000 How to see hidden views in a published workbook? · Issue #953 · tableau/server-client-python · GitHub
[go: up one dir, main page]

Skip to content

How to see hidden views in a published workbook? #953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jacalata opened this issue Nov 9, 2021 · 1 comment
Open

How to see hidden views in a published workbook? #953

jacalata opened this issue Nov 9, 2021 · 1 comment

Comments

@jacalata
Copy link
Contributor
jacalata commented Nov 9, 2021

I have used the new hidden_views in the publish. What we do is migrate from our UAT server to our Prod server. The developer publishes to UAT for testing and hides not-for-display views. What I have a problem with is that I don't know how to get a complete list of views from the UAT workbook because the request only returns unhidden views. I end up doing two publishes. The first publishes the workbook without hidden views and exposes all available views in Prod. I then get a list of all the views from UAT and compare. I then publish to Prod with the minus of the views comparison as hidden_views.

Is there a better way?

Originally posted by @mafleming97045 in #617 (comment)

@barscm
Copy link
barscm commented Dec 6, 2021

Apologies for the 'me too', but we do the same; the issue is that there are two ways to hide the Views: You can either set it up on the workbook, and therefore it's in the XML and can be examined easily, or you can specify the list while publishing - when you do it that way it's not stored in the XML so you need the double publish. To get this functionality you'd need to either change Desktop, so it modified the XML before publishing, or modify the Server API to make a query available... I don't think a client change will address it - but the functionality would be very welcome as it's a problem I've seen in a few places.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0