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

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Anonymous
Not applicable

Modeling - schema

HI , 

what is the more efficient way to work when you have an Order_header table and Order_item level table,

should i work with both table and create relationship between ?

or should i merge the tables in to one table in the model?

 

1 ACCEPTED SOLUTION
amitchandak
Super User
Super User

@Anonymous , You should merge. We prefer star schema, where we would like these two as single fact.

 

If needed Order_header  can also be a dimension

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

HI @amitchandak 

thank you for your advice.

i have a case which we have a authorization process  for purchase orders :

the data is stored on header level:

 

Order Keysign date1 sign date 2 sign date 3
A123132318/02/202219/02/202221/02/2022

thats is why i though to have it on another table in the model , what is your opininon?

 

thanks!

 

Anonymous
Not applicable

@amitchandak 

the issue in this model is that i have orders with line level data, amount qty and so like in classic module,

but , this company have data of Authorization process with every order, and they analzye the time its take to apporove a order, and every order has max up to six signers, so i thoght to hold this infromation in another table in header level to not replicate the data

 

is that a good idea?

Anonymous
Not applicable

@amitchandak 

thanks!!

i was not sure which way is the best practise

amitchandak
Super User
Super User

@Anonymous , You should merge. We prefer star schema, where we would like these two as single fact.

 

If needed Order_header  can also be a dimension

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.