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

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
Laocsulak
Helper I
Helper I

Data modeling for marketplace with same table with movements registered for buyers and sellers

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!

1 ACCEPTED SOLUTION
amitchandak
Super User
Super User

@Laocsulak , Best is two tables with common dimensions like user, date etc

But you can manage with measures.

View solution in original post

1 REPLY 1
amitchandak
Super User
Super User

@Laocsulak , Best is two tables with common dimensions like user, date etc

But you can manage with measures.

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

Check out the June 2024 Power BI update to learn about new features.

RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.