Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
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
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.
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
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 and mark it as a solution 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.
Hi,
please do not close the topic. I still asked questions.
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
FB
Thank you. It seems quite good.
What if i will remove Fact table? What with measures then?
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
FB
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
10 | |
9 | |
8 | |
7 | |
6 |
User | Count |
---|---|
15 | |
13 | |
11 | |
9 | |
8 |