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
Hi all!
I'm working with a client with about 4,000 SKUs in a given year. However, it is a very seasonal business, so only about 1,500 SKUs are in store at any given time. What I need to know is how often the SKU distribution changes - every day, every week, every month? Etc.
My first thought was to do a distinct count of SKUs and then trend that over time, because it is unlikely I'll have exactly the same amount of SKUs each season. But that isn't perfect - ideally I'd have some kind of a matching function and let it tell me when it stops matching, but I'm not sure how to do that with that many SKUs. Any help is appreciated!
Solved! Go to Solution.
This is only part of the complete measure
Matching Percent =
VAR CurrentSKUs =
VALUES ( 'SKU Distributions'[SKU] )
VAR PreviousSKUs =
CALCULATETABLE (
VALUES ( 'SKU Distributions'[SKU] ),
'SKU Distributions'[Date Only]
= MAX ( 'SKU Distributions'[Date Only] ) - 1
)
RETURN
COUNTROWS ( INTERSECT ( PreviousSKUs, CurrentSKUs ) )
Can you please calrify further: "ideally I'd have some kind of a matching function and let it tell me when it stops matching"
Sure thing, and thanks for the help!
Ideally, I'd have some kind of function that would look on a specific day, say day 2, and see how many of the SKUs are the exact same as in the previous day (day 1). If more than 90% of the SKUs were a match, it would return something like "match", if less than 90% were a match it would return something like "Change". Then I would calculate on average how many changes happened during a period, say during 90 days.
While I know there are matching formulas, I'm not sure how to make one that only looks at the previous day, and I'm not sure how to tell it "hey, if it matches 90%, we're good".
It depends. Let's say we're looking at day level, then we can retrieve the VALUES of the SKU's of the current date.
Suppose the dates are continuous (there are other solutions if not) then the previous date would be the current date - 1. We can use this date to CALCULATE the VALUES of SKU's of the previous date. Then simply we can DIVIDE the COUNTROWS of the INTERSECT between the two VALUES over the COUNTOWS of VALUES of the current date. Would that make sense to you?
Hi! Ok, this looks helpful but I'm still confused.
I created a summary table with the date and SKU of each. Now, for this formula, do I need to make a column so it iterates, or a measure?
To me, it seems like I'd do -
I hope by summary table you mean table visual. Then you can create a measure. To retrieve the table of previous SKU's you need to use CALCULATETABLE.
DATEADD might not work being time intelligence function therefore you can use
CALCULATETABLE(VALUES('SKU Distribution Table'[SKUs]),'SKU Distribution Table'[Date Only] = MAX('SKU Distribution Table'[Date Only]) -1)
I'm getting this error -
Here is a screenshot of my table -
Sorry I got distracted by something else.
What is the code you have used. Can you please share? It is a measure orca calculated column?
No worries, thank you SO much for your help!
This is only part of the complete measure
Matching Percent =
VAR CurrentSKUs =
VALUES ( 'SKU Distributions'[SKU] )
VAR PreviousSKUs =
CALCULATETABLE (
VALUES ( 'SKU Distributions'[SKU] ),
'SKU Distributions'[Date Only]
= MAX ( 'SKU Distributions'[Date Only] ) - 1
)
RETURN
COUNTROWS ( INTERSECT ( PreviousSKUs, CurrentSKUs ) )
Ok, so if I'm reading this correctly, this gives me the number of SKUs that are the same as the previous day. Then I need a percent, so I would divide by PreviousSKUs? Or do I need a new variable?
Yes no need for new measure
I tried this this morning - it is back to giving me the error about not expecting multiple values. Here's what I changed the measure to (old one was working perfectly)
You missed the COUNTROWS of "PreviousSKUs
Like this?
Can you share a screenshot?
You have added a column. Go back to the query editor and send some screenshots. It should not a problem to fix it.
SKU Count is just a count of SKUs - at first I thought that was what you meant by values.
Please filter out null
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 |
---|---|
22 | |
21 | |
19 | |
13 | |
12 |
User | Count |
---|---|
41 | |
32 | |
23 | |
22 | |
22 |