Whenever I try to Run Optimizer from the Server menu, I get this error:
#Tableau Desktop & Web Authoring
Hi
@Jeff Wendland
I’m not entirely sure if this will work, but maybe you could try uninstalling Tableau Desktop and installing the latest version.
I have a tableau dashboard that looks like below
My objective is to do the below
a) Compute the % of "Oneill Ltd" (from product family column) that makes up the total sales including other product family values
b) I want to store that ratio output in a seperate calculated field.
When I tried the tableau inbuilt feature table calculation, it is computing the ratio for all rows (which I don't want). I want to now the ratio/percentage of "Oneill ltd" only
#Tableau #Trailhead #Tableau Desktop & Web Authoring #Tableau Public
Hi,
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>
I am using the Tableau MCP get-view-image Tool. Is there a way to download an image with a set filter applied when using a set as a filter on a dashboard? It appears that there is no way to apply a set filter using the REST API View Filter, so I am asking if there is a workaround.
Hey, I ran into the same thing. The REST API view filters (and the MCP tool that uses them) only work with regular fields, not sets. One workaround that worked for me was to filter on the underlying field that the set is built from and just pass the member values. If that doesn’t fit, creating a custom view with the set already applied and downloading that image is another option. Hope that helps.
I’m working on an HVAC website and trying to improve its local visibility. I’ve already focused on the website structure and service-area pages, but I’m curious which factors usually make the biggest difference for Local Pack rankings—Google Business Profile optimization, reviews, citations, or local backlinks?
#Tableau Desktop & Web Authoring
Hello,
My question on the topic detailed below is : is this the expected behavior on Tableau Server or is there something to investigate?
On Tableau Desktop, when you have a table with lots of values, the header values are always on sight even if the number of underlining rows is much higher than the number of rows you can see immediately. To illustrate, you can see
Austria here even if the formatting is in the Middle, and that the middle of that row is much lower in the sheet :
When publishing on server, no matter what the formatting is, the behavior is not the same. I.e. it will only show the value if you are viewing the top, middle or bottom of that row's results depending on your formatting choice :
#Tableau Server
Unfortunately that has always been a limitation of Server/Cloud text tables. I prefer Desktop's behavior. You would need to add a unique hidden column like customer ID to the left of country to get it to appear on every row. But that prevents convenient selection by country.
I use Tableau Desktop 2023.3 to create a dashboard with multiple charts; the data source is a plain text file containing over 100 million rows. The process of generating the necessary extract (Hyper file) completes successfully.
I have a free Tableau Public account, and the dashboard publishes without any issues.
I would like to understand what is happening or how Tableau works, because recently, the data from the text file (the original source) was loaded into a SQL Server 2022 table and aggregated so that it now contains just over 20 million records. I created the corresponding new extract (Hyper file), but when attempting to publish it to Tableau Public, I receive an error message stating that the extract exceeds the maximum limit of 15 million rows.
#Tableau Desktop & Web Authoring
@Roberto Barranco technically, you should not have been able to publish the original dashboard to Tableau Public with a file size greater than 15 million rows of data, to begin with; regardless of data source type.
So, I'm not sure how that was accomplished, perhaps a fluke? Tableau Public has had that 15M row limitation for a very long time.
As we know, things change over the years and Tableau Public is no exception. It's possible that when it was originally published, the version when it was published somehow allowed it to happen. But now, with newer versioning, tighter controls are likely reinforcing the limitation better.
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)
Does anyone have a standard NoSQL database they prefer working with when using Tableau? We are moving away from SQL for our project. Is there a specific NoSQL vendor that plays particularly well with Tableau’s data model without needing constant manual effort?
#Tableau Desktop & Web Authoring
I’d be interested to hear what others have tried here. We’re looking at moving away from SQL too, and the Tableau side of things is something I’d want to get right before choosing a database. Any recommendations from people who’ve actually used one with Tableau?
I've converted my Tableau Repository info into a Tableau Data Source for our analysts to use (Collect Data with the Tableau Server Repository), but I'm confused about how the 'device_type' field is calculated. The data dictionary is here: Workgroups Database.
It shows about half of the views to be accesses by a user/device type of 'Tablet', which can't be true since only perhaps 3% of our users use a tablet or phone to view our visuals.
Can anyone help with the interpretation/calculation of this field?
Thanks!
Andy
Hi Andy!
From what I understand from the documentation, the "device_type" is not what type of device is viewing the dashboard, it's for what type of dashboard was being presented to the client. The explanation for "device_type" is "DSD device type detected" - "DSD" stands for "device-specific dashboard" - this is the type of dashboard layout created in Tableau Desktop. I do not believe this field will track what device was viewing the page, it will only show what dashboard was offered to the user. you can read more about Device Specific Dashboards here: Design dashboards that shine on any device in Tableau 10 | Tableau Software
Hope this helps!
some of the rep wantes to see their territory data on Pulse metrics.
Is it possible to do this on Tableau Pulse ?
or is their any capability of pulse we can achieve.
can you share a scenario or solution if I can achieve this?
#Tableau Desktop & Web Authoring #Tableau Pulse
Hi Himshikha - good news that it works for you and your colleagues; that tells us the RLS logic itself is sound and it is now down to just that one user. When a single follower sees blank/error while everyone else is fine, it is almost always one of two things - and the blank-vs-error distinction tells you which:
1) An ERROR (red banner / cannot load the metric) is usually a data source PERMISSION issue, not RLS at all. This is the number-one gotcha: adding someone as a Pulse follower does NOT grant them access to the published data source the metric is built on. That one rep needs at least View (and typically Connect) permission on the underlying published data source, plus a site role that allows it (a licensed Viewer/Explorer, not Unlicensed). Grant her access to the data source and the error should clear.
2) A truly BLANK metric (loads fine, just no numbers) is an RLS entitlement MISMATCH - her Tableau identity does not exactly match the value your user filter compares against. USERNAME() returns her Tableau Cloud sign-in identity (usually the full email), and the match is exact and case-sensitive. So if your Territory Owner / entitlement value is her display name, an old email, a different domain, or has a stray space or different capitalization, the filter returns zero rows for her - blank. Her name showing in Tableau is not enough; the value in the DATA has to equal her USERNAME() character-for-character.
Fast way to tell them apart and pinpoint it: open the published data source (or the workbook) as the owner, drop USERNAME() and your Territory Owner field side by side on a sheet, then use the 'View As / filter as user' option to impersonate her. You will immediately see whether her USERNAME() finds a matching row (a data/mapping problem = blank) or whether it throws a permission error (an access problem). That one check usually settles which of the two it is.
Diego's advanced-definition idea is good as well, but that is a newer Pulse capability still rolling out - your data-source user-filter approach is the right one to get working now.
If this helps, please mark it as the Best Answer so it helps the next person - thanks :)
Hi everyone,
I’m building a Sankey chart in Tableau and I’m struggling with the correct percentage labels for each level.
My data structure is a pre-aggregated funnel table with these fields:
The Sankey is built using duplicated rows via Table Name:
Then I use a Path calculation to create the left/right side of the polygon:
// Path
IIF([Table Name] = {MIN([Table Name])}, 0, 97)
Path is then converted to Path (bin) with bin size 1.
The funnel logic is roughly like this:
Example filtered view:
Step1 = No Order
Step2_Filter = Pip
Then the first visible split is:
Pip Enabled
Pip Disabled
I want the labels to show users and percentages correctly at each level:
Pip Enabled / (Pip Enabled + Pip Disabled)
Pip Disabled / (Pip Enabled + Pip Disabled)
Pip Enabled → Pip Confirm / Pip Enabled
Pip Enabled → No Confirm / Pip Enabled
Pip Enabled → Card Confirm / Pip Enabled
Pip Enabled → Pip Confirm → Purchased / Pip Enabled → Pip Confirm
Pip Enabled → Pip Confirm → Lost after Confirm / Pip Enabled → Pip Confirm
The Sankey polygon itself works, but the percentage labels are incorrect because the view has multiple technical dimensions:
Because of this, when I try to calculate percentages in Tableau, the denominators are either duplicated or calculated at the wrong partition level.
Current core Sankey calculations:
// Flow Size
SUM([users]) * (1 - [Whitespace]) / TOTAL(SUM([users]))
// Position-L
RUNNING_SUM([Flow Size]) - [Flow Size] + [Whitespace L]
// Position-R
RUNNING_SUM([Flow Size]) - [Flow Size] + [Whitespace R]
// Curve Max Win
[Position Max Win L] + ([Position Max Win R] - [Position Max Win L]) * [Sigmoid]
// Curve Min Win
[Position Min Win L] + ([Position Min Win R] - [Position Min Win L]) * [Sigmoid]
// Curve Polygon Win
IIF(INDEX() >= 50, [Curve Min Win], [Curve Max Win])
For label positioning I currently use something like:
// Label
IF [t] = 6 THEN WINDOW_MAX([Bar Position]) END
What I need help with:
How should I calculate the correct denominators for each Sankey level so that:
Should this be done in Tableau using table calculations, or is it better to pre-calculate parent denominators in SQL and only use Tableau for rendering?
If SQL pre-calculation is the better approach, what grain should the SQL output have to work correctly with Tableau Sankey densification?
#Tableau Cloud
Hi Roman,
You may want to compute the Denominator along both Dimensions (not only along the Bin one) -- and the calc would be simpler (no LOD).
Please find the attached.
Yours,
Yuri
