Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi,
I would like to know what is the best practice to create model that combines sales orders and inovices.
Current state is that I have two fact tables „Sales Order Line“ and „Invice Line“ granularity on both is each line item. Both of them are in separate star schema where common dimensions are „Customer“, „Date“, „Product“ and each fact table is additionaly related to more dimension that are specific for each fact.
„Invoice Line“ fact table has attribute for „Sales Order Document“ and „Sales Order Line Item“
„Sales Order Line“ fact table has this two attributes too.
In theory this two facts should join over Sales Order Line attribute but I do't know is it better to
Thank you in advance.
Best regards,
Petra
Hi @PetrarteP ,
Sorry for that the information you have provided is not making the problem clear to me.
Please provide me with more details about your table and your expected output or share me with your pbix file after removing sensitive data.
Best Regards,
Eyelyn Qin
@PetrarteP , Ideally two facts should not join, not it is good to have such a big common dimension.
What is requirement to join these two ? What expected output for which you need to join these two
Hi,
Basically users would like to slice the Invoice data over attributes/dimensions that are only on sales order (medical data like Surgeon, Patient, Procedure, contracts....). And in general check which sales orders ended with invoice and validate totals.
User | Count |
---|---|
124 | |
108 | |
99 | |
62 | |
62 |
User | Count |
---|---|
137 | |
115 | |
102 | |
71 | |
61 |