The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Six practices for taking Tableau MCP agents from prototype to production (opens in a new tab)

You will learn how to prepare a Tableau data model for agents, scope their tools and data, and build a test and monitoring harness before agents reach end users.

Why read this

The post draws on a regulated-industry customer deployment.

  1. Prepare the data model
  2. Define the agent's role
  3. Follow least privilege
  4. Load metadata into the prompt (optional)
  5. Pre-build queries for known questions
  6. Build evaluation and monitoring
Six practices for moving a Tableau MCP agent from prototype to production, in order

The post describes a large enterprise customer in a regulated industry that moved from Tableau dashboards to custom agents built on Tableau MCP. Off-the-shelf Tableau agents were too broad for the customer, who needed specialized workflows, agents that could act on results, embedding in a purpose-built application, and fine-grained control. Custom agents bring more need for testing, governance and monitoring, so the authors set out six practices.

The first is to prepare the data model. Business logic should live as close to the data as possible: calculated fields for fixed logic, Tableau Knowledge business preferences or field descriptions for logic shared across agents, and agent system instructions for logic specific to one agent. Teams should also remove duplicate fields, describe fields with units and caveats, name them in business terms, hide irrelevant fields and certify the data sources. The TDS Edit API, available in Tableau Cloud from October 2026 and Tableau Server 2026.3, lets teams add field descriptions in code.

The second is to define the agent’s role by answering what problem it solves, which domain it serves, what it can and cannot answer, and how it should respond. The answers shape its data, tools and system prompt. Tableau MCP now supports embedded data sources in 2026.3.

The third is to apply least privilege. The authors removed tools the agent did not need, starting with list-datasources, and pinned the agent to an approved data source ID. Tool scoping is set through environment variables on self-hosted deployments or site settings on hosted Tableau Cloud, and embedded data sources are scoped by project or tag.

The fourth, optional, practice is to load metadata into the system prompt at session start. This removed the get-datasource-metadata call and cut response time by almost 50 percent. The authors warn that this suits agents with one or two data sources and that stale metadata is a risk if schemas change often.

The fifth is to pre-build queries for frequent questions and expose them as custom tools, so the model only explains results. The authors advise against chasing perfect accuracy for open-ended questions, and suggest dashboards for figures that must be exact.

The sixth is an evaluation and monitoring framework: a question bank with correct answers, including refusals, run against each prompt, model and setting version, with LLM-as-a-judge grading for less deterministic answers, release-style versioning, production monitoring of latency, tokens and failures, and a regular review that adds new questions. The authors recommend an established agent observability platform, and they name LangSmith as an evaluation tool they used.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Tableau Data Apps bring governed agentic analytics to vibe-coded apps (opens in a new tab)

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.

  1. Connect your agent via MCP
  2. Prompt your intent
  3. Preview, iterate and verify
  4. 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.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?