You will learn what a Tableau Data App is, where it can be built and published, and how it inherits Tableau's security, semantics and refresh model.
Why read this
The piece is a product overview in beta, so the detail on setup is thin.
Connect your agent via MCP
Prompt your intent
Preview, iterate and verify
Publish and share
The four steps to get a Tableau Data App from prompt to shared link
Tableau Data Apps, now in beta, are custom interactive analytical web apps hosted and powered by the Tableau platform. They separate the visual front end from the query engine, so builders can use AI agents to produce apps quickly while the apps still draw on Tableau’s semantics, connectivity and governance. The article argues that visualization was never the hard part, and that without an analytics platform agent-built apps risk guessing at business definitions, running slow and costly query loops, and leaking credentials or data.
Apps can be built in Tableau Studio or with any third-party agent connected through the Tableau MCP server or Tableau Next MCP server. Apps built in Tableau Studio publish to Tableau Cloud or Server, while apps built with third-party agents can publish to Tableau Cloud, Server or Tableau Next. Inside Tableau Cloud and Server, apps sit in workbooks and query Published or Embedded Data Sources, and in Tableau Next they sit in workspaces and use Tableau Semantics.
Data freshness comes from live connections or scheduled extract refreshes, and federated queries let apps reach heterogeneous sources without copying data. Database credentials stay in Tableau, and object-level and row-level security apply to every user. The getting-started steps are to connect an agent, prompt the intent, preview and verify the logic, then publish and share.
You will know how to structure a Tableau Semantics model for query speed, correct joins, governance and scale, and which build path suits your situation.
Why read this
The piece is practical guidance rather than a release announcement.
Business-driven design and conceptual modeling
Choose a build path
Implement and test iteratively
Design for query performance
Centralize security and standardize
Five groups of practices for building a performant semantic model, in the order the article presents them
The article argues that a semantic model should reflect business concepts rather than database schemas, and that conceptual modeling and stakeholder review should come before joins are configured. It describes three build paths: generating a model from natural language with Tableau Agent, generating one from existing CRM Analytics or Tableau Cloud data, and extending a verified model through composable modeling. It recommends starting from the Salesforce Customer 360 Semantic Model where applicable.
For performance, the guidance is to keep runtime joins to about six or seven, avoid many-to-many joins and expensive operators such as BETWEEN, join on primary keys, set explicit join cardinality, and align default filters with Data Lake Object partitioning. Secondary indexes and pushing heavy transformations upstream into Data 360 batch transforms or Calculated Insights are suggested for very large datasets. Security should be enforced through Data 360 Policies rather than model filters, which are meant for business relevance and can be bypassed by ad-hoc queries.
The piece also advises testing with the Test Model feature and visual checks for join fan-outs, and stress testing against production-scale volumes and concurrent query patterns before rollout.
You will learn the workflow for defining business metrics in OSI YAML, converting them to a Tableau SDM, validating and querying the model, and exposing it to Agentforce and MCP clients.
Why read this
The piece gives the concrete API commands needed to do this.
Ingest CRM data into DLOs
Define metrics in OSI YAML
Convert to SDM JSON
Create and validate the model
Query via Semantic Query API
The workflow runs from ingested data through the OSI specification to a queryable semantic model
The post argues that AI agents need a shared semantic layer so that terms such as revenue and pipeline are defined once and reused across reports, applications and agent answers. Data 360 ingests CRM records into data lake objects, and a Tableau semantic data model adds relationships, metrics and calculations on top of them. Business context is captured first in an OSI YAML specification, which the Salesforce converter translates into an initial SDM JSON file.
The article walks through creating, validating and querying the model with Salesforce APIs, including the converter command, the model creation and validation requests, and a semantic gateway query. It also covers business preferences that steer agent terminology and scope, and verified questions created through Q&A Calibration to make answers more consistent. Agentforce and Claude connected through MCP are shown answering the same pipeline question from the same model.
The post notes that governance through Data 360 classifications, tags and policies can limit access to sensitive data. Its conclusion recommends starting from one business question, defining its terms, validating results, and then extending the shared foundation to more questions and agents.