#Tableau Desktop & Web Authoring177 discussing

Hi, 

I’m not sure whether this adds anything to @寛奈 阿藤  ’s detailed explanation above, but there is one point to keep in mind regarding how NULL values are handled when calculating the difference between Product A and Product B. 

For example, if a missing value should be treated as zero, you can use ZN(): 

ZN([Product B Sales]) - ZN([Product A Sales]) 

If you don’t handle NULLs, the result of the subtraction will also become NULL whenever either side evaluates to NULL. 

Of course, whether NULL should be converted to zero depends on the business meaning of the data, but it may be worth considering when using this approach. 

ex) 

// Difference

zn([Product B Sales]) - zn([Product A Sales]) 

or: 

// B vs A %

IF [Product A Sales] <> 0 THEN 

    (zn([Product B Sales]) - zn([Product A Sales])) 

    / [Product A Sales] 

END

Hi, @Chitti Chitti 

Thank you for reaching out. I’ve created a crosstab version.  

It uses a dual axis and leverages reference lines to adjust the text position.  

Please take a look at the workbook. 

Since I’m not sure how complex your workbook is, it may be difficult to comment from a performance standpoint. 

<sample>

@Himshikha Purohit

Hi, starting november, you may use an advanced pulse definition to add your user filters: 

To create an advanced metric definition: 

Thus, you can create a simple expression like:

[Territory Owner] = USERNAME()

Or you may create more intrincated logic where you have an all access group, and the other people will be applied the RLS

IF ISMEMBEROF('Managers') THEN TRUE
ELSE [Territory Owner] = USERNAME()
END

After you have created the filter (as a calculated field) in the advanced definion dialog, drag it into the filter shelf, drag a date to the time dimension shelf and a measure to measure shelf. Then select apply. 

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 

Jumping back in on the 'highlight' part, Justin - the good news is the dynamic-default approach actually handles all three of your requirements together (show the previous month, highlight it, still fully selectable), and it keeps the month buttons you already built. 

The highlight comes almost for free: if your month buttons are colored by whether the button's value equals the current parameter value - the usual way these button UIs show the 'active' one - then because 'Value when workbook opens' sets the parameter to the previous month on open, that previous-month button is automatically highlighted the moment the dashboard opens. Click any other month and the parameter changes, so the highlight moves with it. That's exactly the 'auto-highlight the previous month, but still selectable' behavior you described. 

If your buttons aren't colored that way yet, add a calc like: 

IF [Your Month Value] = [Time Shift Parameter] THEN 'Selected' ELSE 'Unselected' END 

Drop it on Color on the buttons sheet and give 'Selected' your highlight color. Now whatever the parameter equals - the previous month on open, or whatever the user clicks - lights up. 

So you don't have to choose between the two approaches: Don's relative-date method is great for a rolling window as a filter, but for your specific 'buttons, highlight the active one, default to last month' setup, the dynamic parameter default plus a match-the-parameter color calc gives you all of it while keeping the buttons you have. Hope that gets you there!

Hi,  @SSMK A 

Are you looking for something like the attached example?  

Please take a look. I set up the headers using a dual‑axis. 

<sample>

<sheet settings> 

use dual axis (for header).

Try with the following. 

"123"+CHAR(10)+"456"+CHAR(10)+"789"

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!

You need to create a table calculation to filter the data as shown below: