The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Eight practices for building a performant Tableau Semantics model (opens in a new tab)

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.

  1. Business-driven design and conceptual modeling
  2. Choose a build path
  3. Implement and test iteratively
  4. Design for query performance
  5. 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.

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

Worth reading?