Hi @jaryszek,
Great question and it’s one that comes up a lot in larger models. Both approaches are valid and have their place depending on your model size, team structure, and personal preferences.
If your measures are heavily tied to a specific fact table, keeping them there makes sense. It maintains their business context and avoids complications like drillthrough issues, since those rely on relationships and underlying data structures. As @FBergamaschi said, you can organize them into display folders and hide unrelated columns to reduce clutter. This keeps your model clean and keeps each measure close to its data source.
While if your model is complex, or if you’re managing many KPIs across multiple fact tables or business domains, a dedicated “Measures” table can help. You create a dummy table (like Enter Data > add one column with a blank value), then move all your measures there. Group them using display folders by topic or page (e.g., “Sales KPIs”, “Customer Metrics”). This keeps everything centralized and easier to scan through when you're building visuals or troubleshooting. Tools like Tabular Editor make this approach much easier to maintain.
Just remember if you delete a table (fact or dummy), all measures in it are deleted, so handle that carefully. Meanwhile hidingh unused columns or entire tables (instead of deleting) keeps your model clean without losing anything.
So ultimately, choose the approach that fits your workflow best. If you're the sole developer or want a tidy central place, the Measures table may be perfect. If you’re working with multiple devs or need strong contextual ties, organizing by fact table is safer.
Best Regards,
Hammad.
