#Tableau Server81 人がディスカッション中

I understand, so you could create an underlying text box that essentially says 'Start by filtering in the filter selection pane to the right' and/or have a distinct starting value that is always selected as a starting point.   

We don't know what you're actually working with, but those would be some options to consider.  If you have the link to the idea, could you post it in this thread so that others can upvote it? 

If this response answered your question, please mark it as an Accepted Answer? 

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

Hi Danh, 

Good catch mentioning the MIN(0) workaround — that's likely the real cause here, not a Server bug. 

Why it happens: With MIN(0), the subtitle is just a text label on a hidden dummy mark, not a true axis property. If a filter or RLS reduces the data for that pane to zero rows (or the underlying calc returns NULL), Tableau simply has nothing to plot — so the label silently disappears. Your main title stays because it's likely a straight parameter reference, not dependent on a mark being drawn.

Common triggers:

• The subtitle calc (Actual/Prior/Growth) returns NULL once rows are filtered/RLS-restricted
• RLS often behaves like a context filter, which can affect even FIXED LOD calcs
• "Growth" especially needs a prior period — if that period gets filtered out, there's nothing to compare

How to confirm:

Reproduce the same filter/RLS condition in Desktop. If the subtitle disappears there too, it confirms it's a data issue, not a Server rendering bug. 

Fixes to try:

1. Wrap the subtitle calc in ZN()/IFNULL() so it always returns a value
2. Check if your filters/RLS are set as context filters — this can break FIXED LOD assumptions
3. Make sure the field driving the MIN(0) mark always has at least one row, regardless of filter/RLS state
4. Alternatively, skip MIN(0) and insert the calculated field directly into the worksheet title — titles aren't tied to marks being drawn, so this failure mode goes away entirely

Try it in Desktop first — that'll tell you which fix is needed.

@Kelsie Jacob

I am confused. You said: " On the website, one of my dashboard tabs shows as Automatic fit to the screen size. The other two dashboard tabs have a fixed desktop size." 

Then you say: 

" All three have a fixed size on the desktop file and on the server file." 

Thus my main question is what do you think "automatic fit" involves in the website. If you have your embed code, and explain which part of the code does the "automatic" fit. 

Other questions: 

a. I don't think it is possible to have automatic fit in website and fixed in server.  There is only one fit, the one the workbook in Tableau Server/Tableau cloud is configured. 

b. If your workbook has several dashboards, the iframe that the embed code uses will be set up to the maximum of the widths of the dashboards, and to the maximum of the height of the dashboards.  This means, that the div/table parent container (the div-table should be big enough to handle the size of the children tableau-viz object) 

c. If a dashboard is set to automatic, then in your website you need to create a parent div/table, and set the height and width of the element, so the children element (the tableau-viz component) fills the parent container. 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

@Dan Chissick

Hi, I am trying to give you my best advice of what might be happenning. I got a similar case in the past that I was able to solve following the advices I just gave to you. 

It was a strange case, and metadata related. In the record performance I don't remember if the event was recorded as hundred or more parsing xml events, or simply was not recorded. 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

@Patrick Chinery

You may take a look of: 

Basically, you need to add the complete folder (e.g.

to the exceptions. 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

Hi again Emeric, 

Thank you for your suggestions earlier. I have now followed them and my system works better but one issue remains. 

Current configuration: 

1. Runas now uses a domain account "tableausa" with admin rights on the tableau server 

2. The csv files are on the tableau server shared with

syntax. The tableausa account has permissions on the share. 

3. 

has been added to the allowlist 

I created a new datasource using tableau desktop based on one of the csv files via the fileshare, and converted to a join with a wildcard with no filtering. This works fine and if I add/remove files this is reflected in desktop workbook and datasource. 

I then published the datasource without attached files. When the published datasource is opened via browser the published files are found and can be refreshed. 

Then my luck ran out. I created a workbook via browser based on the new datasource. It opens and finds the published files, but I can not get it to update when files change. It can see all the data and files in the datasource as published, but refreshing to show new data does not work - I have tried F5, menu option to refresh the datasource in "sheet 1" and in the Data Source tab, and opening a new browser. 

My expectation was that when opened the workbook would retrieve data from the files currently in the folder, and that the workbook user could update using menus or F5 when new files were added, but that does not work. 

Do I have the wrong expectations or am I making some mistake? Is it always necessary to edit the datasource when files are added to the wildcard folder? 

-Arvid

I have implemented the solution for day and week. Check the updated workbook attached.

In case anyone else runs into this:  

I learned from our IT department that we have both  internal and public server spaces. I had originally (unknowingly) published to the internal server and later was (unknowingly) viewing content on the internal server, which is why the dashboards didn't appear. The only way to distinguish the 2 spaces is the URL. 

Thanks to all who weighed in. 

Hi @Nigel Smith

Do you have SAML authentication with Microsoft EntraId enabled on your Tableau Server Instance?

If yes, then try this command. 

tsm configuration set -k wgserver.saml.iframed_idp.enabled -v true 

If you have another use case, Trusted Authentication or Connected Apps authentication would help.