You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#614 added the ability to hide views when publishing. However, when trying to publish a workbook that is already on the server, we're only aware of the name of the views that are not hidden.
It would be ideal if we could do the inverse of hidden_views, such as published_views or hidden_views not in [...]. Only way I can think to do this currently is publish in a staging environment to compare the list of views or parse the xml itself.
I found a workaround. You can query the metadata API for the already published workbook luid and ask what views do not have a path value. Those would be hidden.
queryhidden_views($luid: String) {
workbooks(filter:{luid:$luid}){
views(filter:{path:""}) {
name
}
}
}
Originally posted this as desire to have an inverse of hidden_views. So if you always know you're publishing two tabs of "Summary" and "Details" but may occasionally work on an ad-hoc analysis on a new sheet you don't have to worry about updating the list of hidden views.
This is similar to how we're doing it with some pre-processing of the XML, but would be nice to add to TSC directly.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.
Closing as not-planned. Determining the workbook's full sheet list before upload — needed to compute the inverse of hidden_views — requires reading the .twb XML, which lives in document-api-python (https://github.com/tableau/document-api-python), not TSC. For already-published workbooks, jorwoods's Metadata API (GraphQL) alternative in this thread is the other working option. Either surface is outside what TSC can add without duplicating those libraries. If there's a TSC-shaped ask hiding in here — e.g., accepting an include_views list once the user has computed the sheet names themselves — please open a fresh issue.
Activity
bryceglarsen commentedon Sep 22, 2021
Update: able to supplement this with Tableau Document API to get full list of views/sheets and generate list of hidden_views.
jorwoods commentedon Apr 1, 2024
I found a workaround. You can query the metadata API for the already published workbook luid and ask what views do not have a path value. Those would be hidden.
bryceglarsen commentedon Apr 5, 2024
@jorwoods We need a way to integrate our thread from slack 😆
This is good for things that already exist on the server, but think adding
include_viewswould have to work by leveraging Document API under the hood.jorwoods commentedon Apr 5, 2024
Oh, are you looking to get the sheets that aren't hidden by being parts of dashboards or a viz in tooltip?
bryceglarsen commentedon Apr 5, 2024
Originally posted this as desire to have an inverse of
hidden_views. So if you always know you're publishing two tabs of "Summary" and "Details" but may occasionally work on an ad-hoc analysis on a new sheet you don't have to worry about updating the list of hidden views.This is similar to how we're doing it with some pre-processing of the XML, but would be nice to add to TSC directly.
github-actions commentedon Aug 18, 2026
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.
jacalata commentedon Aug 25, 2026
Closing as not-planned. Determining the workbook's full sheet list before upload — needed to compute the inverse of
hidden_views— requires reading the.twbXML, which lives indocument-api-python(https://github.com/tableau/document-api-python), not TSC. For already-published workbooks,jorwoods's Metadata API (GraphQL) alternative in this thread is the other working option. Either surface is outside what TSC can add without duplicating those libraries. If there's a TSC-shaped ask hiding in here — e.g., accepting aninclude_viewslist once the user has computed the sheet names themselves — please open a fresh issue.