Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
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.
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 |
---|---|
83 | |
75 | |
64 | |
39 | |
34 |
User | Count |
---|---|
107 | |
56 | |
52 | |
48 | |
40 |