Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello,
I work for a startup where we have a marketplace where we have buyers who make purchases and sellers who make sales.
The model of the transactions table is built in the next way: For example, if a customer makes a purchase in 3 installments, the transactions table registers 6 movements. 3 movements with the features of the installments of the buyer and 3 movements with the features of the installments of the seller.
What is the best way to model this, using the same transactions as the fact table for all movements or separating it into two fact tables, one for movements related to sales and one for movements related to purchases?
Thanks in advance!
Solved! Go to Solution.
@Laocsulak , Best is two tables with common dimensions like user, date etc
But you can manage with measures.
@Laocsulak , Best is two tables with common dimensions like user, date etc
But you can manage with measures.
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
71 | |
70 | |
38 | |
27 | |
26 |
User | Count |
---|---|
97 | |
96 | |
59 | |
44 | |
40 |