Joining orders to customers without double counting
Choose a semantic-model join approach that preserves correct metric grain when enriching a dashboard.
The risk Orders are one row per order, but the account-history table can hold multiple rows per customer. A direct workbook join might enrich the view or might multiply the metric. Semantic-model join design decides whether self-serve users see a trusted number or a subtly inflated one. Preserve metric grain The semantic model should define joinable entities and the allowed path between them. When a descriptive field has many historical states, you need a rule for which record is valid at the metric grain. Common shortcut Join the latest table in the dashboard and hope the totals still match. The…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in