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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
Anonymous
Not applicable

Best way to create a multi-table report

Hello everyone. Im still a newby at Power BI, so I am sorry if this is a silly question.

To sum up: I want to show a report with the ammount of times every type of transaction is done.


The problem is that I have the type of every transaction located in a different table. Example:

NCOmDl5

The report would use the count of Products.idproduct for each Transaction.Transaction type. Now, this would be easy if I could make a new table with only those registries, but unfortunatelly both Products and Transaction have a huge ammount of data and I want to avoid increasing the refresh/load times as much as I can.

As you can see in the (odd) example, Products and Transaction have one field in common, the barcode. Every Transaction.itemBarcode must exist in Product.productBarcode, maybe multiple times, but not every Product.productBarcode exists in Transaction.itemBarcode

I tried to make a relationship between those tables so I could use a DAX Function to retrieve data, but when I was about to create that new relationship this message appered:
WlR4Slh
I am not really sure about whats wrong there, but I can guess that it will increase the refresh/load time...

Right now I'm not sure about what should I do, so I wanted to ask you guys!

What would you do in my place? And, is there any way to do it efficiently?

Thanks a Bunch!

1 ACCEPTED SOLUTION
Greg_Deckler
Community Champion
Community Champion

Many-to-many is not necessarily bad. You could also look at changing the cardinality between PRODUCTS and DATASOURCE to Both.



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

View solution in original post

2 REPLIES 2
Greg_Deckler
Community Champion
Community Champion

Many-to-many is not necessarily bad. You could also look at changing the cardinality between PRODUCTS and DATASOURCE to Both.



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...
Anonymous
Not applicable

It worked out! Thanks Greg!

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