Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.

Reply
geiratatea
Frequent Visitor

Power BI problem in data model and in a matrix visual

Hi!

 

I am making a data model and reports in Power bi using REST API to get all information about workspaces, users, datasets, reports and so on. The data model is simple. The workspace table is in the middle and is related to dataset, report, user table

 

datamodel.png

 

In my report I want to create a matrix with two levels Workspaces and Reports. I want to show number of workspaces, number of reports and number of users. It is perhaps a silly report but my problem is following. The matrix is behaving strange.When having workspacename and reportname as fields in Rows and just adding count of reports in Values, everything seems ok. But when I add number of workspaces in values, all reports is being displayed under every workspaces in the report. I was not excepting this at all.  It seems to calculate well on the top level. Why are all reports being displayed under every workspace (top level) in the matrix? A second thing is that I want to only show values on the level (you may think there is a third level users). I only want to show measure values on the level. How can I create measures that can do this? If you see anything wrong in my datamodel, please tell. Thank you

 

Best regards

geir

 

report.png

1 ACCEPTED SOLUTION
AlexisOlson
Super User
Super User

Brukere is not filtered by Rapporter, so the count is always the same regardless of which one is on that row. It's basically doing a cross-join of workspaces and reports and computing the count for each combination whether or not the combination exists since the count isn't dependent on the report.

View solution in original post

2 REPLIES 2
AlexisOlson
Super User
Super User

Brukere is not filtered by Rapporter, so the count is always the same regardless of which one is on that row. It's basically doing a cross-join of workspaces and reports and computing the count for each combination whether or not the combination exists since the count isn't dependent on the report.

Hi again.

 

I took th easy way out of this making all relationship both directional. The performance will not suffer very much since the data amount is rather small. But I am not very satisfied. Of course it may have been easier making a classic fact table in the middle. But if I have used the original one directional relationship, I must have created dax measures that have been intelligent from what ever I have used of combinations from these other tables. The group/workspace id is the only relationship key between the tables but there exist other virtual as user email, dataset that can be used. Or what do you think?

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors