topic Re: How structurized and make order with DAX statements - best practices in DAX Commands and Tips

How structurized and make order with DAX statements - best practices

jaryszek — Fri, 27 Jun 2025 14:03:15 GMT

Hello Guys,

How to make a structure to find easily all measures? How do you organize it? Maybe you are putting them into folder with page name or you have seperated measure table?

How to not look for them in whole model while analyzing data?

Best,
Jacek

Re: How structurized and make order with DAX statements - best practices

FBergamaschi — Fri, 27 Jun 2025 14:13:15 GMT

My suggestion is to avoid a table for measures (you lose the ocntext in which they work and will have issues in the drillthrough if you use a table for measures), but rather in each Fact Table they work on, create folders categorizing the measures. Then hide everyting apart from measures and dimensions, so you find them easily (you can hide multiple columns at the same time and move multiple measures at the same time in the model view)

If this helped please give kudos and/or mark as a solution

Best

Re: How structurized and make order with DAX statements - best practices

jaryszek — Mon, 30 Jun 2025 07:45:47 GMT

Thank you. It seems quite good.

What if i will remove Fact table? What with measures then?

Re: How structurized and make order with DAX statements - best practices

Anonymous — Mon, 30 Jun 2025 11:06:25 GMT

Hi jaryszek,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are looking for a way to organise your measures into a single place. As FBergamaschi has already responded to your query, kindly go through the response and check if it solves your issue.

I would also take a moment to thank FBergamaschi, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.

Best Regards,
Hammad.
Community Support Team

Re: How structurized and make order with DAX statements - best practices

Anonymous — Wed, 23 Jul 2025 02:20:06 GMT

Hi jaryszek,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution. And if you're still looking for guidance, feel free to give us an update, we’re here for you.

Best Regards,

Hammad.

Re: How structurized and make order with DAX statements - best practices

jaryszek — Fri, 04 Jul 2025 13:11:40 GMT

Hi,

please do not close the topic. I still asked questions.

Re: How structurized and make order with DAX statements - best practices

Poojara_D12 — Sat, 05 Jul 2025 05:23:48 GMT

Hi jaryszek

To keep your Power BI model organized and make it easy to find and manage measures, it's best practice to create a dedicated "Measures" table. This is a dummy table with no actual data, created solely to store all your DAX measures in one place, separating them from your fact and dimension tables. Once you’ve created this table, you can move all existing measures into it and then organize them using display folders. Display folders help categorize measures by topic, such as by report page (e.g., "Sales Page KPIs"), business area (e.g., "Finance Metrics", "Customer KPIs"), or function (e.g., "Time Intelligence", "Ratios"). Using a consistent naming convention for your measures—such as prefixing them with terms like "Total", "Avg", "YTD", etc.—makes it easier to identify them at a glance. Tools like Tabular Editor allow you to batch-manage folders, rename measures, and even document your DAX logic, which is especially helpful in large models. This structured approach prevents the need to search through the entire data model every time you want to find or modify a measure, greatly improving efficiency and model maintainability.

Re: How structurized and make order with DAX statements - best practices

FBergamaschi — Sat, 05 Jul 2025 07:40:44 GMT

If you remove a table, you lose the measures included. So you can keep it and just hide the columns. The model should include measures in fact table and columns in dimensions (sually hiding the keys)

Best

Re: How structurized and make order with DAX statements - best practices

jaryszek — Mon, 07 Jul 2025 08:10:23 GMT

Curious about 1 measure table approach vs measures added to fct table...

What do you think about solution proposed by FBergamaschi Poojara_D12 ?
Why your solution is better?

Best,
Jacek

Re: How structurized and make order with DAX statements - best practices

Anonymous — Tue, 08 Jul 2025 16:41:26 GMT

Hi jaryszek,

Thanks for getting back to us. I understand you still have questions, and we're here to help. Please take your time, and feel free to clarify your remaining questions or add any new details, and we'll do our best to assist you further.

Best regards,
Hammad.

Re: How structurized and make order with DAX statements - best practices

Anonymous — Sat, 12 Jul 2025 17:57:42 GMT

Hi jaryszek,
Hope everything’s going smoothly on your end. As we haven’t heard back from you, so I wanted to check if the issue got sorted.
Still stuck? No worries just drop us a message and we can jump back in on the issue.

Best Regards,

Hammad.

Re: How structurized and make order with DAX statements - best practices

jaryszek — Mon, 14 Jul 2025 07:41:26 GMT

We are waiting for Poojara_D12 why MeasureTable if better than Measure table per fct table as FBergamaschi proposed.

Please do not close topic.

Re: How structurized and make order with DAX statements - best practices

Anonymous — Mon, 21 Jul 2025 04:51:21 GMT

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.

Re: How structurized and make order with DAX statements - best practices

Anonymous — Wed, 23 Jul 2025 02:20:36 GMT

Hi jaryszek,
We noticed there hasn’t been any recent activity on this thread. If your issue is resolved, marking the correct reply as a solution would be a big help to other community members. If you still need support, just reply here and we’ll pick it up from where we left off.

Best Regards,

Hammad.