Skip to content

Boreon MCP Layer · Salesforce Agentforce

Tableau, Salesforce CRM and CRM Analytics, into Tableau Next.

Tableau Next lives inside Salesforce, on Data 360. The Boreon MCP Layer brings three kinds of content into it: your Tableau Server or Tableau Cloud workbooks, your Salesforce CRM's own Lightning reports and dashboards, and your CRM Analytics dashboards. Charts become Tableau Next visualizations and dashboards become Tableau Next dashboards, together in one workspace. Nothing converts until its data is proven real, and nothing goes live until a person says so.

Book a working session Migration Options

Salesforce is one of our closest partners.

Tableau Server or Tableau Cloud

Sales Overview

  • Revenue by region
  • Pipeline trend
  • Top accounts

The grounding gate

  1. Maps to the Sales semantic model
  2. 12 of 12 fields are in the model
  3. 48,210 real rows behind it

Tableau Next · Sales workspace

  • Revenue by regionVisualization
  • Pipeline trendVisualization
  • Top accountsVisualization
  • Sales OverviewDashboard

Live, after a person approved it

Illustration · sample data

The grounding gate comes first.

A Tableau data source converts only when its data is real from end to end. If a single field is missing, the whole data source waits, and the plan tells you which fields to add.

  1. It maps to a semantic model

    Each data source is matched to a Data 360 semantic model: the one built on that same data, or the one you name.

  2. Every field is in the model

    Every field the workbook uses has to be in that model. One missing field holds back the whole data source.

  3. The data is real

    The model has to answer a query, with real rows behind it, counted live.

From Salesforce CRM: your Lightning dashboards, rebuilt in Tableau Next.

Salesforce CRM's own reports and dashboards move too. Each Lightning report becomes a Tableau Next visualization through the same converter as Tableau, its columns resolved to your CRM objects and fields, and each dashboard keeps its layout on Tableau Next's grid.

Lightning dashboard12 columns

  1. Gauge
  2. Funnel
  3. Pie
  4. Table

Tableau Next dashboard48 columns

  1. NumberMatches Lightning
  2. BarsMatches Lightning
  3. DonutMatches Lightning
  4. Text tableMatches Lightning
Illustration · sample data
  1. 01

    Ask what's in the CRM

    Every Lightning dashboard, listed by folder. Name the one you want, and its plan is written for you to read.

  2. 02

    The data lands first

    The plan lists the Data 360 streams it creates or switches on through your org's CRM connector, and a semantic model related the way your CRM relates its objects. The run waits for the rows before it builds.

  3. 03

    Reports become visualizations

    Columns resolve to your CRM objects and fields, Record Count becomes the object's row count, and each component's chart chooses the mark.

  4. 04

    Sharing carries

    Folder sharing becomes Tableau Next shares, and a person approves the run with the typed phrase.

  5. 05

    Proven, chart by chart

    Afterwards every chart's numbers are compared with Lightning's, group by group, and each asset says it was migrated from Salesforce CRM.

New Data 360 streams use Data 360 credits, and the plan lists every one before anything runs.

How the Agentforce Ohana helps with a CRM move

From CRM Analytics: your dashboards, rebuilt in Tableau Next.

CRM Analytics dashboards move too, page by page. Their recipes show where every row comes from, so each dashboard gets its own semantic model in Data 360, and each widget becomes a Tableau Next visualization that keeps its titles, legends, sorts and number formats.

CRM Analytics dashboard2 pages

  1. Won revenue
  2. Revenue by month
  3. Pipeline by stage
  4. Cases by region and priority

Tableau Next dashboard2 pages

  1. Won revenueMatches
  2. Revenue by monthMatches
  3. Pipeline by stageMatches
  4. Cases by region and priorityMatches
Illustration · sample data
  1. 01

    Ask what's in CRM Analytics

    Every dashboard, grouped by its app. Name the one you want, and its plan is written for you to read.

  2. 02

    The recipes show the way

    Each dataset's recipe tells the plan which objects it reads, the lookups it walks and its formulas and filters. Recipe formulas become calculations in the semantic model, and recipe filters carry to every chart that reads the dataset.

  3. 03

    One semantic model per dashboard

    Each dashboard gets its own model in Data 360, shaped like its recipes and fed by Data 360 streams through your org's CRM connector. Before anything is built, the model must answer with real rows.

  4. 04

    Pages and widgets carry

    Pages become Tableau Next pages and widgets become visualizations, with their axis titles, legends, sorts and number formats. Text widgets keep their rich text, and a person approves the run with the typed phrase.

  5. 05

    Proven, chart by chart

    Afterwards each chart's numbers are asked of CRM Analytics and of Data 360, group by group, and must agree exactly. Each asset says it was migrated from CRM Analytics.

Proven on three multi-page CRM Analytics dashboards: 41 of 41 charts match CRM Analytics, group by group, and draw in Tableau Next.

How the Agentforce Ohana helps with a CRM Analytics move

What becomes what.

Once the gate passes, your content lands in one Tableau Next workspace, bound to the semantic model.

From Tableau
On Tableau In Tableau Next
Worksheets Tableau Next visualizations
Dashboards Tableau Next dashboards, laid out on its grid
Marks, shelves, color, size, label, detail and tooltip The same encodings on each visualization
Filters: value lists, excludes and ranges Tableau Next filters
Permissions Tableau Next sharing: Manager, Editor, Commenter or Viewer
People and groups Salesforce users, matched by email, and public groups, matched by name
From Salesforce CRM
In Salesforce CRM In Tableau Next
Lightning reports Tableau Next visualizations
Lightning dashboards, on a 12‑column grid Tableau Next dashboards, on its 48‑column grid
Gauge Number
Funnel Bars
Pie Donut
Table Text table
Record Count The object's row count
Folder sharing Tableau Next shares
From CRM Analytics
In CRM Analytics In Tableau Next
Dashboards Tableau Next dashboards
Pages Tableau Next dashboard pages
Widgets: charts, tables and numbers Tableau Next visualizations
Recipes and their datasets A semantic model in Data 360, one per dashboard
Recipe formulas Calculations in the semantic model
Recipe filters Filters on every chart that reads the dataset
Axis titles, legends, sorts and number formats The same on each visualization
Text widgets Their rich text, on the dashboard

Plan it, rehearse it, then a person says go.

A Tableau Next migration runs one conversation at a time, and it never skips a step.

  1. 01

    Ask in natural language

    Name the workbooks or the project that should move, and the workspace they should land in.

  2. 02

    Read the plan

    Every item in order, data sources before the workbooks that use them, with what the grounding gate found spelled out.

  3. 03

    Rehearse it

    A dry run reads and converts everything exactly as the live run will, and writes nothing.

  4. 04

    A person approves

    A signed-in person types the approval phrase. No model or agent can start a live run.

  5. 05

    Watch it land

    Each item ends done, already there, skipped with the reason, or failed in Salesforce's own words.

The Einstein Trust Layer, beside you the whole way.

The AI that reads your request and explains each step thinks through the Einstein Trust Layer, so every prompt stays grounded and masked, and the model keeps nothing. Your Agentforce agent can answer questions about the move, too.

Which dashboard should live in Tableau Next first?

Pick one, from Tableau, Salesforce CRM or CRM Analytics. We'll ground its data in Data 360, plan the move with you and rehearse it, and it goes live only when you say so.

Book a working session See it live at ai.boreon.com