#Tableau Desktop & Web Authoring토론 중인 항목 165개

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).

Hi, @Andrzej Polachow

Thank you for reaching out. Using the technique I shared earlier, it's also possible to create multiple representations as shown in the attachment.  

Please take a look. (The sample is kept simple for demonstration purposes.) 

<sample>

It looks like the numbers, symbols, and numbers are right‑aligned properly.  

What do you think?

@Patrik Melichercik the outline feature really only outlines the borders of a geography.  The datavis.blog

has a set of examples of what can be done with the fairly new OUTLINE() function if that's what you're asking for.  There are limitations. 

What you're trying to do, which is now the first that I'm seeing it mentioned in the thread, is more of a drill-down process Region --> Country --> State/Province which is an entirely different concept and process.  They can be complicated, and not always work as intended.  You can look at

as well. 

Insofar as user-friendliness, this for me is more of a training issue than anything.  A notation in the dashboard would suffice to tell the user how to use the dashboard, and still get the functionality you're looking for.  They'll just need to hit the ESC key once/twice to exit out of a polygon that has been selected. 

I don't currently see a method of using 'on select' at this point without a greater level of involvement and likely some type of additional layering which may or may not break things due to too many competing actions, whether filter action, highlight action, parameter action and so on. 

Sorry that we weren't able to help.  Maybe those additional links will help point the way for you.  Best, Don

You can do the Union in your first Custom SQL script itself as shown below 

SELECT A,B,C 

FROM XYZ 

WHERE Condition1  

UNION ALL 

SELECT A,B,C 

FROM XYZ 

WHERE Condition2 

UNION ALL 

SELECT A,B,C 

FROM XYZ 

WHERE Condition3  

Hi,  @Xin Yuen

Kevin’s method produces the following results: the minimum value across the entire view is 85,951, and the maximum is 131,994. 

85,951 − (131,994 − 85,951) × 2 = −6,135 

Since the article takes the larger of this value and 0, the lower bound of the Y‑axis becomes 0 in this case. 

Here, I’m introducing an alternative workaround. This approach assumes that all values used in the RUNNING_SUM are positive and that the cumulative values do not decrease along the Timepoint. 

Under this assumption, the overall minimum of the cumulative values can be taken from the first Timepoint of each Year, and the overall maximum can be taken from the yearly totals. These can be obtained using LOD calculations and then applied to the same formula used in the article. Please refer to the sample. 

<sample>

<calc>

 Also, since unverified AI‑generated answers are increasingly being posted, please be cautious with responses that do not include concrete samples. 

Hi,

Yes, this can be achieved in Tableau Pulse.

The recommended approach is to implement Row-Level Security (RLS) on the underlying Tableau data source, rather than trying to apply RLS directly inside the Pulse metric.

For example, suppose you have:

Rep | Territory | Sales

• John → North
• Sarah → South
• Mike → West

You can create an entitlement/security mapping between the Tableau user and Territory, and use USERNAME() / FULLNAME() or a Data Policy to restrict the rows each user can access.

Then create the Pulse metric from this secured data source.

So when John views the Pulse metric, the metric and its insights are calculated only from the North territory data available to John. Sarah would see South, and Mike would see West.

This is particularly useful for sales organizations where every rep should follow the same Pulse metric definition but only see their own territory.

Tableau's documentation also confirms that Tableau Pulse metrics respect RLS applied to the underlying published data source.

Reference: https://help.tableau.com/current/online/en-us/pulse_set_up.htm

Hi, 

Yes, this can be achieved using a dynamic calculated field with TODAY() instead of hardcoding M1, M2, etc.

For example:

DATEADD('month', -1, DATETRUNC('month', TODAY()))

This will automatically return:

• Aug 2026 → Jul 2026
• Sep 2026 → Aug 2026
• Oct 2026 → Sep 2026

You can then use a parameter action for the button-style month selection while limiting the selector to the current + previous quarter months. This keeps the solution dynamic as the months/quarters change.

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