Sales → product, store, date
Inventory → product, warehouse, date
Finance → account, organization, period
Map → keys, hierarchy, history
Unify who and when before comparison
A store ID, warehouse code, and cost center may describe related organizations without being the same entity. Joining names causes gaps and false matches.
Conformed dimensions provide governed keys, names, hierarchies, attributes, and history at a declared grain.
Preserve source differences
Keep source keys and map them to common entities. One store may map to several warehouses or cost centers; document cardinality, effective time, and owner.
Route uncertain mappings to unknown or review instead of forcing reconciliation.
Version hierarchy and history
Regions, divisions, categories, and tiers change. Current-only values rewrite history; effective intervals support historical and current views.
Declare the default view and let questions select another explicitly.
Govern shared dimensions across teams
Business owners define entities, data teams maintain keys and quality, and consumers confirm scope. Identify dependent facts, metrics, and reports before change.
Keep local attributes in domain dimensions unless they truly need cross-domain reuse.
Accept with cross-fact questions
Align sales and inventory by product, store, and date and reconcile finance and operations by organization and period, including many-to-one mapping and unknowns.
BuildTable can be evaluated for shared models; mapping, history, and cross-domain publishing require project confirmation.
Public references
Build an AI-ready data foundation
Download BuildTable or talk with us about your data modeling scenario.
Download BuildTable