Why Are Tableau Custom Views Broken or Missing?

Start with the original published view. Can the affected manager open it, and can the owner find North Weekly Sales from its View menu or the workbook’s Custom Views tab? Compare those two accounts before deciding the saved state has been deleted. Capture the affected URL, owner and last known correct North result for the investigation.

Tableau’s Custom Views guide explains that saved views are private by default. Sharing availability depends on site role, user visibility settings and Share Customized capability. An administrator can inspect ownership and, where permitted, transfer it. Removing an owner from the site also removes their Custom Views; plan ownership changes before removing the account.

Use the source and owner columns to investigate which saved view the reader needs.

If North Weekly Sales still exists but its values or controls changed, compare the latest workbook release with the version that last worked. Tableau’s maintenance guidance identifies renamed workbooks or sheets, deleted-and-republished workbooks, replaced sources and removed fields as causes of breakage. Updating existing content is not the same operation as deleting it and publishing a new workbook.

Avoid using deletion as a first troubleshooting step. Deleting a Custom View also removes its dependent subscriptions and alerts. If a replacement is necessary, first record the intended regional result and delivery requirements so the manager does not lose the reporting handoff while the source is investigated.

Write down the symptom before choosing the fix. “Missing” can mean the manager cannot find a private view; “broken” can mean the view exists but no longer represents the agreed report. Those require different evidence and different owners.

If the saved view uses a default value and the source default changes, the saved view can follow that change. Check whether North was explicitly selected or inherited as the default.

A missing control does not establish that all data is now visible, and an email arriving does not establish that its contents are still correct. For the North example, compare a known regional total and a deliberately different region. That is a more useful acceptance check than confirming that the dashboard loads.

Give content repair and recurring delivery named owners. The report author can investigate the source; operations can keep track of the next expected email and communicate a delay. If the manager needs a temporary file, have its content checked and label its actual period rather than forwarding an unverified automatic result.

For North Weekly Sales, agree the expected Region and week ending 18 October 2026 before making further changes. Keep the last known correct sample and record whether the issue began after a release, an ownership change or a change in access. If the existing recurring job could send misleading content, pause that job while the result is unresolved.

Have the author compare the source with the agreed requirement. Tableau’s safe-update instructions recommend testing saved states and updating suitable existing content in place. Follow the procedure’s published-source assumptions; republishing is not a universal repair.

Compare the saved reporting requirement with the changed source before trusting the next automatic output.

If an approved replacement view is needed, save it from the intended North selections and check its output. Recreate the required subscription explicitly when the old one was deleted; a new view with a familiar name is not evidence that the old delivery still exists. Confirm the next schedule and recipients with the manager.

Where operations also needs managed files, messages or additional destinations, an ATRS Single Schedule can hold that delivery configuration. Follow the ATRS Single Schedule guide: select the linked Tableau account and valid Item Path, enter the actual report parameter names, values and types, and preview the source. Retest existing jobs if those source details changed.

For the controlled sample, use North and the agreed date only where the report exposes those supported parameters. Set the required PDF or spreadsheet output and approved test destination, then use Tools > Test. Open the received file and reconcile its region, period and totals before resuming Monday 08:30 delivery in the intended time zone. Configure exception handling and assign an owner for failures or unexpected empty output.

The ATRS delivery workflow can keep file production, routing and execution review together. It does not remove the source dependency. Once the corrected result is accepted, tell the manager which view or job is now authoritative so an obsolete bookmark does not become the next reporting route.

For a workbook with many consumers, use an inventory to identify saved views before a release or account change. The List Custom Views REST method is available from API 3.18. An administrator can list site Custom Views and their associated workbooks, source views and owners. A workbook-filtered request is:

GET /api/<api-version>/sites/<site-id>/customviews?filter=workbookId:eq:<workbook-id>
X-Tableau-Auth: <tableau-session-token>

Use a supported version and an authorized session. Process pagination rather than assuming one response is complete. For non-administrators, an unfiltered request returns only owned views; filtered results also depend on permissions and site user visibility. An absent result from one account is not proof that the saved view was deleted.

Retain the inventory with the release record and use it to choose representative checks, including North Weekly Sales. Record the expected owner, region, period and dependent delivery requirement. The listing identifies objects; it does not prove their data is correct or that their subscriptions reached recipients.

For deeper investigation, Tableau describes comparing working and changed .twb files. Saved interactions reference element identifiers and values. Use the comparison to isolate changes; validate any repair in staging rather than assuming identifier edits will recover the view.

After the release, compare the inventory and actual report results with the accepted baseline. For delivery managed in ATRS, also review the configured source and a received sample. Keep content validation and delivery confirmation as separate evidence so a successful export does not hide a wrong region or destination.

If the problem is native visibility or a damaged saved state, repair that specific issue in Tableau first. Keep the correct North view, its owner and a small representative result available for the next workbook change.

Consider the ATRS Tableau report scheduler when the broader requirement is maintaining a recurring export-and-delivery job. Start with a valid report and approved values; compare a controlled received file before making the job recurring.

Explore maintained Tableau report emails and delivery

Considering ATRS for recurring reports after workbook changes? Share the guide with the content owner and operations team to review source access, deployment and delivery requirements.

Download the ATRS Internal Evaluation Guide