Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hello all!
I've been pulling data from Unleashed, an inventory/sale management system, to report on our data.
The data model is broken up into a heap of different fields such as:
Sales Order, Sales Person, Sales Invoice, Product, etc.
I've built out relationships between all of them based off the Sales Order (as it's the core) but I'm having issues slicing the data as when I'm trying to report on the INVOICED sales (completed sales orders) it defaults to registering the invoice against the month the sales order was created, not when the invoice was created (at the close of sale). We could have months between an order being created and an invoice being sent out due to lead times on our product.
I've got the Sales order linked to a date table and something in there is where the problem is. I can't link the invoices to the date table as it would create ambiguity between the invoice and order fields.
Anyone got any idea here? I'm sure there's an easier way to solve this that i'm missing.
@shannondean84 , Here
1. sales order will act as a dimension
2. One additional copy of sales order will act as fact
3. if join between Sales order is 1-M, then a merged table of Sales order and Invoice will act as fact
so 2 fact and 1 dimension are need from these two tables
Then you have to use common dimensions and active/active joins as per need
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
92 | |
83 | |
71 | |
49 |
User | Count |
---|---|
143 | |
121 | |
111 | |
59 | |
57 |