#Tableau Public49 diskutieren mit

Hi, @Wylie Goodman

The tooltip configurations do not appear to be identical.  

In the BRPC Project Timeline sheet, the tooltip contains only “Link:” and the <ATTR(Link)> field has not been inserted. In the working Community sheet, <ATTR(Link)> is included and displayed as a hyperlink. 

Berkshires Forward Timeline

Community

First, could you compare the settings to see if there are any differences?

@Harry Goyal

Hi, if you are using Tableau Desktop Free: 

a. Create a directory (as an example in your Desktop) 

b. Then open Tableau Desktop, go to File Menu and change Repository Location:

If you are using Tableau Public, you would need to change a config key in the Windows registry: 

a. Start Button, Registry Editor. 

b. You will need to go to under the Computer\HKEY_CURRENT_USER\Software\Tableau to your current Tableau Public Release

Computer\HKEY_CURRENT_USER\Software\Tableau\Tableau Public 2026.2\Directories

c. Select the Directory Branch, and right clic and select new String Value:

d. Give it a name of Repository:

f. Click on Ok and open Tableau Public Desktop. You will notice the folder will be filled with the default repository directories:

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, @SSMK A

I may still not fully understand what you’re trying to achieve, but are the values shown in the Sample diagram what you’re referring to? 

For checking purposes, I’ve displayed each value as well. 

Since the processing is done with an LOD calculation, please be aware that if you need any filter operations, you’ll have to use a Context Filter. 

<sample>

<calc>

Hi Varun,  

I ran into the same error when opening a Tableau Desktop workbook in Tableau Public. It happens because Tableau Public only supports extracts, and the workbook was using a live connection.

I also didn’t realize at first that Tableau Desktop is now available for free (with some publishing limitations).

To fix it, try opening the file in Tableau Desktop—it should prompt you to replace or convert the data source (like Superstore/SuperDepotSales) into an extract from your local machine. Once you create the extract, it should work fine in Tableau Public.  

If you find this answer helpful, please mark this as an accepted answer. 

Regards 

Rajneesh

Adding to Farhan's and Steve's helpful comments, I think your finding that a single worksheet works, a web-authored dashboard works, but a Desktop-authored dashboard does not gives us a very useful way to narrow this down further.

Before rebuilding any existing dashboards, I would try creating a very small test workbook in Tableau Public Desktop 2026.2.1:

1. Create one simple worksheet.
2. Publish it and confirm that its thumbnail appears.
3. In the same workbook, create a new dashboard containing only that worksheet.
4. Publish again without adding any other dashboard objects, containers, images, extensions, etc.
5. Check whether the thumbnail becomes blank.

If the worksheet thumbnail works but the minimal dashboard becomes blank, that would be a particularly useful reproducible case because it removes most workbook-specific factors from the equation.

I would also try publishing the same minimal workbook from a different Desktop Public version, if one is available to you. If the exact same workbook produces a thumbnail from another build but not from 2026.2.1, that would provide stronger evidence that the behavior is related to the Desktop build / publishing path rather than the dashboard design itself.

One other thing I would avoid for now is rebuilding the production dashboards in Web Authoring just to fix the thumbnails. Since the published dashboards themselves render correctly, and Steve mentioned that a Tableau Public thumbnail issue is already being investigated, rebuilding could involve a lot of work for something that may ultimately be resolved on the service side.

So, as a next step, I think a minimal reproducible workbook would be very valuable:

Worksheet → thumbnail OK

If that sequence is reproducible, it should give the Tableau team a very clean test case and may also help determine whether this is the same known thumbnail issue Steve mentioned or something specifically related to Desktop Public 2026.2.1.

Hope this helps with the investigation!

Hi @Wiwit Setyaningsih

I'll reiterate both yours and @Gohar Clients thoughts on the compute by - definitely on the right track. Here's where I can take things by working on that and a small tweak and additional calc: Workbook re-attached.

First thing you'll see is a new calc: YoY (Latest Year  Only)

IF LAST()=0THEN [YoY]END

(NB: I also renamed your "Calculation 3" to YoY). 

The new calc just says "only return a value for the last year* in the view". We do have to tell Tableau that we care about the year for this part of the calc. And what we end up with is a nested table calc where the compute by for one part is different to the other! 

Right click and edit the table calculation pill on Rows:

First up I'm working on the "Latest Year Only" calc as you can see in the top drop down. And I tell it to compute by specific dimensions and year only. So the latest year should be the last (LAST()=0) in the window. 

Now I change the drop down to the "YoY" calc and tell this to compute by specific dimensions again, but this time Year and Month (in that order)

NB: Show calculation assistance is quite handy here as I can check that I am indeed seeing values 13-24 in the window. Now you might be thinking "hang on, how did my lookup -1 work in that case?!?"  and you'd be right! I also changed the lookup to be a lookup by -12 so now we're looking back to the month 12 months ago. 

The lack of an ELSE in the second calc is what supresses the previous year from showing ... it's still available to the calc as we've "filtered" using a table calc so that happens late in the order of operations ... and those are the "nulls" shown by the >12 nulls indicator. 

Finally I CTRL+click and drag the pill from Rows onto Mark Text too so that I don't need to repeat the nested compute by there. 

Let me know if this helps!  

Compute by is often fiendish enough without (a) nesting; and (b) your great workaround for side-by-side without a discreet pill on Columns! 

Ta, Steve

Hi, 

Are you looking for something like the attachment? Please take a look. 

The idea is to create parameters with ON/OFF values and then set up corresponding fields that switch OFF/ON in response, allowing you to control visibility through parameter actions. A dedicated sheet is prepared for the checkbox, where ON and OFF are represented using shapes. Please see the details below. 

This was implemented using only standard features. The display switching is handled by configuring a DZV. 

<sample>

 <parameter>

<calc>

<dashboard action>

 <check box sheet settings> 

Using the “off‑on” field from the checkbox sheet, the display switching is achieved through a parameter action. 

-Configuration for the checked state. Please pay attention to the shape and color.

*Sorry if the square shape is a bit confusing, but the checkbox frame itself is represented using borders.”

-Configuration for the unchecked state. Please pay attention to the shape and color.

<Dashboard DZV settings>

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