How does Tableau Next compare to traditional Tableau in practice?
I recently attempted to recreate an existing Tableau dashboard in Tableau Next. Here's what stood out.
What Makes Tableau Next Different?
Unlike traditional Tableau, Tableau Next is built around Salesforce's Data 360 platform and a semantic layer that defines how business data should be interpreted.
Rather than simply building individual visualizations, users can create reusable metrics that provide a consistent understanding of business performance. Combined with Salesforce's AI capabilities, Tableau Next is designed to make analytics more accessible and actionable across an organization.
Where Tableau Next Shines
1. Dashboard Layout and Design
One of the most noticeable improvements was how easily I could organize dashboard layouts.
Compared with traditional Tableau's containers and layout configuration, arranging visualizations in Tableau Next felt considerably more intuitive.
2. Dashboard Filter Management
In traditional Tableau, applying a filter across multiple worksheets often involves configuring individual sheets or using the Apply to Worksheets option.
Tableau Next makes this easier by allowing users to specify which visualizations a filter should affect directly from the dashboard.
This centralized approach makes managing dashboard interactions much more convenient.
3. Metrics and Business Insights
Tableau Next's metrics are particularly promising. Rather than simply displaying an aggregated value, metrics can provide additional context around trends, changes, and performance.
For organizations monitoring operational KPIs across departments, this approach could be particularly valuable.
Where Tableau Next Falls Short
Despite these improvements, recreating my dashboard exposed several frustrations.
1. Geographic Coordinates
Plotting exact locations was surprisingly difficult. My original Tableau dashboard used calculated X and Y coordinates to display individual projects on a map.
Tableau Next struggled to interpret these calculated fields. Geographic fields stored as recognizable location names might provide an easier experience, but precise coordinate-based mapping proved challenging in my case.
2. Parameter Configuration
In traditional Tableau, parameter lists can be populated from existing field values.
I couldn't find an equivalent option in Tableau Next. Instead, I had to manually enter every year from 1998 onward.
For parameters with dozens of possible values, this quickly becomes tedious.
3. Calculations and Metric Dependencies
Creating metrics also required more configuration than expected.
Although the resulting metrics can provide richer insights, setting them up requires carefully defining calculations, semantic models, and time dimensions.
At one point, my dashboard couldn't retrieve a Population Served metric because it couldn't locate the associated semantic model.
Even configuring a straightforward year-based filter became unnecessarily complicated.
4. Missing Familiar Interactions
Another frustration was the absence of familiar right-click context-menu functionality during my workflow.
Small interactions like these might seem insignificant, but they can meaningfully affect the speed of dashboard development.
So, Which Should You Use?
Tableau Next appears particularly well suited to organizations already operating within Salesforce, especially those looking for standardized KPIs, reusable business metrics, and AI-assisted analytics.
Traditional Tableau, however, still feels more flexible for hands-on analytical exploration, custom calculations, and precise geographic visualizations. Tableau next is much better for when you need to deliver a quick standardized business dashboard however Tableau shines when we want to deliver insight more creatively and possibly with more depths ( due to greater chart customisability)
My experience suggests that Tableau Next prioritizes consistency and accessibility, while traditional Tableau offers greater control over the analytical development process.
The real question isn't necessarily which platform is better, but which approach best supports the organization and its users.