Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
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?
Solved! Go to Solution.
@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
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 Key | sign date1 | sign date 2 | sign date 3 |
A1231323 | 18/02/2022 | 19/02/2022 | 21/02/2022 |
thats is why i though to have it on another table in the model , what is your opininon?
thanks!
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 , 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
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
110 | |
99 | |
80 | |
64 | |
58 |
User | Count |
---|---|
148 | |
111 | |
93 | |
84 | |
66 |