#Tableau Desktop & Web Authoring155 debatiendo

Hi David,  

Before you file it as a bug, check if those titles were ever edited by hand. When you open Edit Title and change the font, size or colour there, Tableau saves that formatting on the title text itself. The Custom Themes help page says this directly: even with Override, an imported theme doesn't replace formatting done in the rich text editor, and Edit Title is that editor. A template workbook is the classic place for this, because someone styled the titles once and it stuck. Also check you picked Override and not Preserve when you imported the theme, since Preserve keeps whatever formatting the workbook already has.  

Easy test: add a new sheet to the same workbook and don't touch its title. If the new one comes out in 

#878a8f

 Tableau Semibold 14 and the old ones don't, it's the per-title formatting, not the theme.  

I checked the behaviour with Format > Workbook > Worksheet Titles on Superstore (screenshot): the sheet with the untouched title changed, the one I had formatted in Edit Title kept its own font and colour 

To fix the existing titles: right-click the title, Edit Title, click Reset, OK. That puts it back to the default title and the theme can style it again. If a title had custom text you'll have to retype it after the reset, just don't change the font while you do.  

Chris's set idea is the right way, I built it on Superstore to make sure it really drives the zone (screenshots below). A few details that made it work:  

Create a set on Mission ID (right-click the field > Create > Set) and use it in place of the Mission ID filter, so every sheet that was filtered by Mission ID now has the set on Filters showing IN. Then right-click the set > Show Set, and on the card's menu choose Single Value (dropdown). For your users it looks almost the same as the dropdown they have now, the only difference is there's no (All) option in single value mode.  

Keep the set dropdown outside the container you hide. If it sits inside it, it disappears with the section and nobody can switch back.  

The visibility field must be one value for the whole workbook, so the whole comparison goes inside the braces:  

{ FIXED : COUNTD(IF [Mission ID Set] THEN [Milestone Rank] END) > 0 }   

Written as { ... } > 0 it won't show up in the list, that's the bit Chris mentioned. And because it's a FIXED, normal filters don't affect it. If another filter on the dashboard should count too (date, region...), right click it and Add to Context.  

Put the milestone sheets in one tiled container, select the container, go to the Layout tab, tick Control visibility using value and pick the field. When it's False the container goes away and the tiled items around it take the space, so no blank area.  

In my test the field is "does the selected state have any order with a 50% or bigger discount": Texas shows the section, California hides it. Same structure as yours, just swap in Mission ID and Milestone Rank.  

That message comes up because your dashboard is set to add new objects as Tiled. Tiled is the default, so everything you drag in snaps into the layout and into whatever container is under the mouse. Holding Shift just flips it for that one drag, which is why it keeps asking.  

If you mostly want floating objects, change the default instead. In the Dashboard pane on the left, just under the Objects list, there are two buttons: Tiled and Floating. Click Floating and every new object you drag in will float, no Shift needed. Screenshot below shows where it is.  

For something that is already on the dashboard, click it, open the small dropdown arrow on its border and tick Floating (untick it to put it back in the layout).  

Just keep in mind a floating object sits on top of the containers, it is not part of them. If you want it to move and resize with a container, it has to be tiled inside that container. 

Create:

BAT

tableau isn’t fully supported. Syntax highlighting is based on BAT.

WINDOW_AVG(SUM([Measure]))

Then:

1. Drag it to Rows.
2. Make it Dual Axis.
3. Synchronize Axis.
4. Change Marks type to Line.
5. Format as a dashed line.

Glad you got it working. What you found points to the actual cause, though: the server isn't sending the GoDaddy intermediate certificate along with yours. Chrome and Edge quietly fetch a missing intermediate on their own, so the site looks fine in the browser. Tableau Desktop doesn't do that, so it fails unless the intermediate is already in that machine's certificate store, which is why installing the .p7b fixed that one PC.  

It may also explain why it broke exactly at renewal: GoDaddy has been moving renewals to a new intermediate (R1), so if the server still has the chain file from the old certificate, it won't match the new one.  

If you fix it on the server instead, you won't have to repeat it on every Desktop machine. Tableau Server wants PEM files, not the IIS ones. Download the certificate again from GoDaddy and choose Apache (or Other) as the server type, which gives you your .crt plus a second file with "bundle" in the name. That bundle is the chain. In TSM go to Configuration > Security > External SSL, add it as the certificate chain file next to your cert and key, save and apply pending changes.  

Or from the command line:  

tsm security external-ssl enable --cert-file .crt --key-file .key --chain-file tsm pending-changes apply  

To check what the server sends: openssl s_client -connect yourserver:443 -showcerts. You should see your certificate and, under it, GoDaddy's intermediate (the bundle can add a cross-signed root too, so two or three is fine). If only yours shows up, the chain isn't being sent. Applying the change restarts services, so do it out of hours 

Hi, it depends on where the name lives. I'll assume it's a field name. If it's a member alias or text in a sheet title, the answer is a bit different.  

If the 17 reports connect to one published data source and the item is a field in it, rename it there once: open the data source in Desktop (or Edit Data Source on the server), rename the field, and publish it back over the same data source. Shefali and Yasin say existing workbooks keep the old name. I'm not sure that's true in every case. As far as I know a rename made in the published data source usually shows up in connected workbooks the next time they're opened, unless a workbook renamed that field itself (then its local name wins). Calculations keep working either way, because they point at the field's internal name and not its display name. Text typed by hand into a title or caption won't change. Please test it with one workbook first, it only takes a few minutes, and then you know for your setup.  

If each workbook has its own embedded data source, there is no bulk rename in Desktop or web authoring. You either edit them one by one or script it. A .twb is XML and the displayed name is the caption attribute of the field's column element (for .twbx it's the .twb inside the zip), so a script can change it before republishing. Tableau Support doesn't support editing the XML, so keep backups.  

Publishing many workbooks at once: tabcmd publish with --overwrite in a loop, or the REST API. Those two are the officially supported options. Tableau's Python libraries, Tableau Server Client (for the REST API) and the Document API (for editing workbook files), are open source from Tableau and supported through GitHub and the community, not through support cases. 

Hi Narender, had a look at all four. Mostly small things, and the chart types are generally fine.  

Viz 1. Bars are right for comparing rates. Some of the 100% bars (Undefined under No Deposit, and several of the Refundable ones) are probably very few bookings, but they look as important as Online TA. Add the booking count to the tooltip or label (n=12 style), or filter out segments under a minimum. Also City Hotel and Resort Hotel are sorted differently, so it's hard to compare the same segment across the two. Use one fixed order.  

Viz 2. Careful with seasonality here. This dataset covers arrivals from July 2015 to August 2017, so July and August appear three times and every other month only twice. Adding up all years makes the summer peak bigger than it really is. Use one full year (2016) or show average bookings per month per year. The orange bars are labelled "Count of Is Canceled" in the legend, which reads like cancellations, so rename that to Bookings. And for the channel / customer type part of your question, filters only show one at a time. Small multiples, one small chart per channel, would answer "does the pattern differ" much better.  

Viz 3. The title is the same as viz 1, I think it should say country. A diverging palette suggests there is a meaningful middle, so either centre it on the overall cancellation rate (then orange/blue means below/above average) or use a sequential palette. Countries with only a handful of bookings get the strongest colours, same issue as viz 1, so a minimum bookings filter helps. Portugal is by far the biggest origin in this data and probably deserves its own callout. I'd also remove the Latitude/Longitude (generated) and parking space filters, readers won't use them.  

Viz 4. I couldn't tell what each bubble is without hovering, so label them or use shape for the other dimension. Average days on the waiting list is close to zero for most of the bubbles, because most bookings never wait at all. "% of bookings that waited" would show much more. Bubble size for 0.28 to 1.15 special requests is hard to read, and this one is trying to answer four things at once, so I would split it in two.  

Labels: only the highs/lows or the marks you talk about in the text. Tooltips don't look overloaded to me. 

Those messages (Processing request, Computing models, Preparing results) are the loading spinner for the dashboard you're going to, so the click on the button is most likely working. It's the target dashboard that never finishes, and an error after about an hour sounds like a query timing out somewhere.  

To check that, open the dashboard the button goes to directly, from the workbook's list of views or its URL, without using the button. If it hangs the same way on its own, the buttons aren't the problem. That would also fit with Hideaki's simple test working fine.  

If it hangs by itself, a performance recording will show what it's waiting for. A site admin has to allow it first (Settings, the workbook performance metrics option). Then add :record_performance=yes to the view URL (after a ? or an &, depending on whether the URL already has one) and load it. Once the view finishes or errors, click Performance in the toolbar. The recording lists each query with how long it took, so the slow one stands out.  

Also, is any of this on a live connection through Tableau Bridge? If so, check the Bridge client is on a current version as well, since the site itself just got upgraded. 

Republishing won't fix this one, so I'd stop spending time on it. If Web Edit shows the dark blue box and only the published view shows it white, the formatting is saved correctly in the workbook. So what changed is most likely the Cloud viewer, not your workbooks. The timing matches Tableau Cloud moving to 2026.3 this month, and there is another post here this month about things behaving differently after that upgrade. You can see your site's version under the help (?) menu, About Tableau Cloud.  

What I'd do: 

- First open one of the views in a private/incognito window. If it is still white there, it is not a browser cache thing. 

- Check

for filter or parameter formatting in 2026.3. If it's already logged you can follow it there. 

- Open a support case and attach a tiny workbook that shows it: Superstore, one dropdown filter with a dark blue background and white text, published to your site. A small repro gets looked at much faster than a production workbook. Mention that it affects more than 100 workbooks.  

As a stopgap on the dashboards people use most, you could set the filter text box background to white and the font dark, so it reads fine whether or not the bug is there. Not your standard, but it stops the tickets, and you can switch back once it's fixed.