Data model objects
The inventory, with the category as the schema.
Read Salesforce Data 360 into one governed layer
Data 360 is the catalogue. A semantic model is the contract you define once. Tableau Semantics is the question surface it feeds. TabTotal reads all three, read-only, and writes nothing.
It names the flow that signed in
Sign-in runs as a chain. A Connected App with client credentials comes first. A username and password flow is the fallback. Then the Data 360 token exchange. The connector says which one answered, and which endpoint served it.
- The working flow is remembered and reused
- An org without Data Cloud gets one clear answer, and it is remembered
- It can reach salesforce.com and force.com, and no other host
Semantic models arrive as first-class objects
Reading the org lands data model objects, with the category as the schema. Semantic models land as objects in their own right, rather than as metadata hanging off something else.
- Metric expressions carried on the column level metric tag
- Contract members keyed by model and name. Two models can define the same measure
- Synonyms feed term resolution
One sync, three warehouses
One sync pulls every backend you have connected. Drift parks and is approved one warehouse at a time.
- One warehouse never reports on another
- The same table in several warehouses is one logical object
- Where any two disagree, that is a governance finding naming the pair
What it reads
Semantic models
First-class objects, with their metric expressions.
Governance
What the catalogue already records, inherited, not retyped.