New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Sales says one customer count, support says another, and both pulled from the same warehouse.
What you'll have at the end
One shared customer dimension that both fact tables join to, with matching totals to prove it
You need
Two departments' own fact tables, each already joined to a customer dimension that department built from its own source system, both living in the same warehouse.
Not covered
Keeping every source system's customer record synced in real time, or standing up a full identity-resolution platform; this covers building and wiring in one shared dimension by hand.
Leans on
Fix a warehouse total that's doubled
Go there instead when the extra rows trace back to one dimension's own change-history rows for a single key, not two departments' separately built customer tables.
Untangle a many-to-many relationship with a bridge table
Reach for this one instead when one customer legitimately belongs to several groups at once, not when two departments' own identifiers for the same customer simply don't line up.
Checked 25 Aug 2026
Part of the Data Warehousing cookbook