r/tableau • u/TelevisionPlus5203 • 10h ago
Tableau Studio has gone GA and you can try it for free!
r/tableau • u/TelevisionPlus5203 • 10h ago
r/tableau • u/heyroll100 • 5h ago
Hi, i just went through Datacamp's Fundamentals of Tableau track. (lots of hours) and have gotten experience making basic charts.
I want to learn more but there is SO much information out there i don't know where to start. Can anyone please either point me in the direction of a recommended list or study structure I can follow or can provide their suggestions on what to do next? Really appreciate it, thank you!
r/tableau • u/BringingBread • 9h ago
Do you guys share your workbooks across different teams/departments? People ask me for mine because some of the data sources get pretty complicated. Technically this stuff belongs to the company but it still bothers me because I spent so much time doing the research to get them to work.
r/tableau • u/balakrishnatrt1 • 2d ago
Hey people,
Does tableau support minimum number of users like 2/3 licenses (one creator , one explorer) or is there a minimum as part of tableau standard package ?
We are considering a potential migration from tableau to metabase since our team size is small (70 and possibly <45 active users). Many are basically using claude artifacts. So, I thought maybe keeping min. Tableau users is a good fallback option.
We did test Metabase features - they seem good so far. But let me know if it’s not or if there are some serious cons.
Thanks in advance.
r/tableau • u/Wit-tor6 • 4d ago
I do this thing now where if a number is within about 3% of what I expected, I dont chase it. I call it match and move on. Our old analyst would spend a whole day tracing a tiny variance in a huge category. Id rather save my energy for the stuff that actually moves. My boss hasnt complained once in eight months. Is that bad? I spent this morning pulling eileen checks for a reset and it hit me I apply the same close enough to shelf counts. Maybe thats the line?
r/tableau • u/Cute-Matcha-Latte • 4d ago
So for one of my classes, we have to use tableau as a tool of data visualisation. For this assignment, we have to create a dashboard on a topic of our choice and I was wondering if you guys had any advice on layout, colours, fonts, etc. This assignment is worth 70% of my grade but this assignmeent is asking for a lot at the moment. I have a screenshot of my completed dashboard (in greyscale as i'm a bit unsure about what to make stand out). Any advice is appreciated!
r/tableau • u/KaloLeto • 4d ago
Hi friends, I have a data project where I have a Sales table containing three different date fields: Open Date, Closed Date, and Signed Date. I also have a Dates table that maps each calendar date to its corresponding fiscal year.
From a dashboard performance standpoint, would it make more sense to create three relationships or use three LEFT JOINs? I will have some fairly complex calculations and want to make sure I'm setting up the data model efficiently.
For context, here's the level of detail (LOD) for each table:
My initial thought is to use three LEFT JOINs, connecting each date field in Sales to a separate instance of the Dates table.
Am I thinking about this the right way, or would relationships be the better approach?
Let me know if I need to provide any more information for this to make sense. Thank you in advance :)
r/tableau • u/hahahehe0000 • 4d ago
Hi r/tableau! We're a student team, and this is Part II of our progress draft for a dashboard on the 2019 World Happiness Report.
Context: 156 countries, each with a Happiness Score (0–10, from the Gallup World Poll) and the estimated contribution of six factors to that score (GDP, social support, healthy life expectancy, freedom, generosity, perceived corruption).
The dashboard reads top to bottom in three sections:
Color rule: orange/blue = happiness level; plum/gray = factors.
We'd love any feedback to improve our visualizations.
- Is it clear that GDP, social support, and health make up most of the gap?
- Is the box plot easy to read for a general audience, or would a simpler chart work better?
- Does the dashboard read as one story?
Thank you in advance for your time!

r/tableau • u/AutoModerator • 4d ago
Please use this weekly thread to promote content on your own Tableau related websites, YouTube channels and courses.
If you self-promote your content outside of these weekly threads, they will be removed as spam.
Whilst there is value to the community when people share content they have created to help others, it can turn this subreddit into a self-promotion spamfest. To balance this value/balance equation, the mods have created a weekly 'self-promotion' thread, where anyone can freely share/promote their Tableau related content, and other members choose to view it.
r/tableau • u/No_Ambition8323 • 5d ago
For me, it was “Compute Using” in table calculations. My running totals and percent of total kept giving strange numbers, and I had no idea why. I kept changing settings until it looked right, without really understanding it.
What finally helped was thinking of it as: “Which direction should Tableau move when it calculates?” Across the table, down the table, or within each group. Once I got that, everything made more sense.
What about you?
Let’s help others skip the struggle!
r/tableau • u/spencer-vale-11 • 6d ago
Mid-size SaaS, about 400 dbt models on Snowflake, Looker for most things and a handful of Tableau workbooks finance built themselves. Three weeks ago we renamed customer_tier to plan_tier in staging and carried it through to the mart. Looker broke right away and we fixed the LookML that afternoon.
Two of the Tableau workbooks had custom SQL against the mart and ran on extracts, so the refresh failed, the failure emails went to whoever built them in finance, and Tableau kept serving the last good extract. We found out when our controller asked why enterprise revenue hadn't moved in weeks.
Exposures would have put both workbooks on the DAG, but nobody declares one for something finance built in 2023. I'm trying to work out what people actually run for impact analysis before merging a column change, because at the moment it's a grep through the LookML and nothing for Tableau.
r/tableau • u/CRM_is_watching • 7d ago
r/tableau • u/jrunner02 • 8d ago
Just got Data Apps working in my Tableau Cloud instance. Vibe coding dashboards makes dashboarding fun again. I can just tell Claude "add a sankey chart" and it just does it no questions asked. To be fair, I haven't asked it to do anything complicated, like low level security or anything that would require a level of detail calculation but it doesn't seem like it'd be a tall task.
As simple as creating data apps is, it makes me wonder if data apps alone are enough to keep people on Tableau as it has become exorbitantly expensive.
Internally we're looking at other options. Claude dashboards were viewed as a data retention issue, but other options also exist that allow you to vibe code dashboards.
Vibe coding dashboards has become so popular We are combatting shadow BI from cheaper tools. Tools that don't have the same governance and security. This is risky move but analystsnbut people are doing it because they have access to these tools.
What are you guys doing to combat Shadow bi? Are you guys already coming off of Tableau? Have you tried data apps? What do you think of them?
r/tableau • u/No_Ambition8323 • 9d ago
I had a running total of sales by month. But when I filtered to show only the last 3 months, the running total started over from zero. Not what I wanted!
The reason: normal filters remove the data before Tableau calculates the running total.
The trick that fixed it: filter using a table calculation instead.
Table calculation filters run after the running total is calculated, so the numbers stay correct. They just hide the rows you don’t want to see.
Has anyone solved this a different way? And are there other places where you use this LOOKUP trick?
r/tableau • u/Evening_Hawk_7470 • 11d ago
so every quarter our data team used to lose an entire week to the same fire drill: Finance would bring a Tableau deck to the board prep meeting, Product would pull up Superset, and RevOps would open an Excel export and all three had `dashboards showing different numbers` for "Net Expansion ARR" and "Active Paying Accounts."
when we audited why we had `inconsistent metrics across dashboards`, the root cause wasn't dirty raw data in Snowflake. our dbt staging and core models were clean. the problem was that over 5 years, analysts had built 240+ calculated fields directly inside `.twbx` workbooks (`business logic stuck in Tableau`), while another team had written slightly different `CASE WHEN` filters inside Superset virtual datasets and AI text-to-SQL prompts.
every time our pricing tiers or refund rules changed, someone had to manually hunt down and edit formulas across 30 workbooks (`redefine metric in every report`).
here is what failed when we tried to fix this in the warehouse, and how we actually built a `single source of truth for metrics` using a headless semantic layer:
1. why "just put all metrics in dbt mart tables" broke on day 3
our first instinct was to pre-calculate every metric as a column in wide dbt `mart_` tables. that works fine for simple additive sums (`gross_revenue`), but it falls apart immediately on:
- **non-additive ratios:** if you pre-calculate `net_margin_pct` or `conversion_rate` at the daily/regional row level in a dbt table, and a Tableau user drags that column onto a quarterly chart and averages or sums it, the math is completely wrong (`SUM(numerator) / SUM(denominator)` has to be evaluated dynamically at the query's exact `GROUP BY` grain).
- **distinct counts across time:** `COUNT(DISTINCT customer_id)` by day cannot be summed up to get monthly active customers.
- **multi-fact fan-outs:** joining `subscriptions` (grain: contract) to `invoices` (grain: monthly bill) and `product_usage` (grain: daily user) in a flat wide table causes row duplication that silently inflates sums unless every BI author writes complex LOD (`{ FIXED ... }`) expressions in Tableau.
2. comparing dbt Semantic Layer (MetricFlow) vs. Cube (`cube.dev`)
we ran a 3-week pilot testing both `dbt Semantic Layer` and `Cube` to govern `metrics as code` outside the BI tools:
- dbt MetricFlow was great if we only wanted metric definitions living in our existing dbt repo, but at the time its downstream connector story for our exact mix (Tableau + Superset + an internal React portal + Excel) felt restrictive, and it didn't solve our Snowflake latency/cost issue because it still compiled raw queries against the warehouse on every slice.
- Cube (Headless Semantic Layer) to let us define `cubes` (entities, joins, base measures) and `views` (curated business datasets) in version-controlled YAML, and expose them simultaneously via a Postgres-compatible SQL API (for Superset, Tableau, and DataGrip), REST/GraphQL APIs (for our embedded web app), and a native MCP server (so Claude and our internal Slack bot query governed metrics instead of guessing raw SQL).
3. how the workflow looks now
- zero calculated fields allowed in BI: we instituted a rule that Tableau and Superset workbooks are strictly presentation layers. if a metric needs a filter (`is_test_account = false`, `status != 'voided'`, or complex `SUM(a)/SUM(b)` ratio math), it gets committed as a pull request in our Cube YAML repo (`metrics as code`)
- chasm-trap proof joins: because Cube knows the `primary_key` and `one_to_many` relationships between `subscriptions`, `invoices`, and `usage`, a business user can pull dimensions and measures from all three into one chart and Cube isolates the aggregations into separate subqueries before joining and now no more Tableau LOD hacks.
- pre-aggregations in Cube Store: to keep Tableau live connections from lagging on 60M+ rows, we added `rollup` pre-aggregations on the top 12 views. live queries return in around 150ms without needing fragile Tableau `.hyper` extract schedules
now.. for teams who managed to kill metric drift across multiple BI tools (Tableau / Power BI / Superset / Excel): how did you enforce a single source of truth without analysts going rogue and creating local calculated fields again?
r/tableau • u/AutoModerator • 11d ago
Please use this weekly thread to promote content on your own Tableau related websites, YouTube channels and courses.
If you self-promote your content outside of these weekly threads, they will be removed as spam.
Whilst there is value to the community when people share content they have created to help others, it can turn this subreddit into a self-promotion spamfest. To balance this value/balance equation, the mods have created a weekly 'self-promotion' thread, where anyone can freely share/promote their Tableau related content, and other members choose to view it.
r/tableau • u/sparrow_Lilacmango • 12d ago
I have to approximate what percentage of arrests are made in a day split between different sets of hours, but it's driving me up the wall trying to figure out how to split up the data point containing the hours. I only want to look at data from 2021-2022 too. I think I have to use datepart but even looking at tutorials this is confusing
r/tableau • u/No_Ambition8323 • 13d ago
My dashboards look great on a laptop, but on a phone they’re a mess. Charts get squished, filters are hard to tap, and people have to scroll a lot.
Right now I’m trying a few things:
Using Device Designer to make a separate phone layout
Putting key numbers (KPIs) at the top
Stacking charts in one column for mobile
But it still feels like a lot of extra work.
How do you handle this?
Do you build one dashboard for both, or separate ones?
Fixed size or automatic size?
Any layout tips that made a big difference?
Would love to see examples if you have any!
r/tableau • u/Exciting-Speech-4945 • 13d ago
So my prof said that the visual should "pop out" like if it's a pie chart it should be popped out like 3-d as in a cuboid, I am not sure if I can do that in tableau, I put in some borders and different colours to make it look like that
r/tableau • u/bigboi5374 • 14d ago
I have a Measure Names filter (multiple values, with "Show Apply Button" on) in Tableau Cloud. If I untick a measure and then type in the filter's search box, the measure gets ticked again: the untick reverts to the last applied state. New ticks survive searching fine; only unticks get lost.
Is this expected behavior, or is there a setting or workaround to keep unticks while searching? Pressing Apply before every search works, but it's clunky with a long list of measures.
r/tableau • u/Both-Machine-5619 • 14d ago
Hello,
I've been getting this error when trying to type into a filter on my tableau public dashboard: Uncaught TypeError: Cannot read properties of undefined (reading 'collation')
This started without me publishing any new changes. I've tried republishing the workbook, refreshing the data sources, and I still get the error. There isn't an error when I open the workbook in tableau desktop and all of the fields appear valid. Any advice extremely appreciated!