Tableau Feed

It's a bit interesting that when someone is developing out a filter using the Filters Card, the very feature you're looking to use is available just as you've described, the ability to search then select different values, then click apply (all values need to be deselected first):However, the end-user doesnt' necessarily see that feature, they'll only see what's given to them in a multi-select list as you've noted.  Perhaps the closest you could get to the above would be to right-click the filter on the View (where it is traditionally placed on the right side); then, from the list of options, select Customize, then select or rather check Show Apply Button.

In that manner a filter that is already pre-deselected, then the user can use a wildcard search on the filter, the click apply per each selection.  So for example, Region is used from Sample Superstore data in a filter and it is already displayed with all values unselected.  The apply button has been invoked.  User searches for Central and selects that value then clicks Apply button:

I think that would be the closest you're going to get to that type of Excel-like search and apply feature.  Obviously, the end-user would need to again deselect all for their next instance of using it.  But if the workbook is initially saved in a deselected state, then it will reflect as much when the user invokes use of it. 

I haven't searched for it, but you could also create an Idea in the

for the same feature to be developed in the future.  As to the why's/wherefores, sorry I don't have any good explanations for you as to how/why this was originally developed out. 

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)

 I understand that your goal is to align the "▼" or "▲" symbols vertically.

While I am not sure if this completely meets all your requirements, here is a method you can try:

1.  Create separate calculated fields for the values before and after the symbol

• Example 1 (For Numerical Value): A calculation that displays -33.0
• Example 2 (For Symbol & Rate): A calculation that displays ▼-7.3%

2. Split the placeholder into two fixed values

Create two dummy fields with slightly shifted X-axis coordinates to separate the position of the "Numerical Value" and the "▼ Growth Rate".

• Example 1 (For Numerical Value): placeholder_1 $\rightarrow$ Formula: 0
• Example 2 (For Symbol & Rate): placeholder_2 $\rightarrow$ Formula: 0.2 (or a slightly larger value like 1 to place it on the right)

Place both on the Columns shelf as a Dual Axis:

Place AVG(placeholder_1) and AVG(placeholder_2) side-by-side on the Columns shelf, then set the second one to Dual Axis.

Edit both axes and set a Fixed Range (e.g., -1 to 1).

 (Note: Using SUM on the Columns shelf can cause positions to shift depending on data row counts, so AVG is recommended. Changing placeholder to AVG only controls the layout position and will not affect the actual values displayed in your text marks.) 

3. Adjust the layout (text alignment) on each Marks Card

• placeholder_1 (Left Axis / Numerical Value):
  • Place only the "Numerical Value" into the Text mark.
  • Set alignment to Right (so numbers expand to the left).
• placeholder_2 (Right Axis / Symbol & Rate):
  • Place only the "▲/▼ Growth Rate" into the Text mark (do not include the numerical value).
  • Set alignment to Left (so "▼" starts at the fixed 0.2 line and expands to the right).

If the text overlaps at 0.2, please adjust the dummy value as needed. Note that changing the value might automatically reset the fixed axis range back to "Automatic," so if that happens, please re-edit the axis range to "Fixed." 

 In my test, setting placeholder_2 to 

1.1 and fixing the axis range from -1 to 2

 worked very well.   

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.

@shweta jadhav this question/post has been asked before on the Slack Channel for Tableau.  As already recommended, please contact Support and file a support case for resolution.  This is not immediately resolvable. Open a Support Case:  Submit a case

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 @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

@YU shyke

Hi, maybe you are affected by this issue: 

If the provided solutions don't work for you, consider creating a support case: 

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 

@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