Forum Discussion
Backlog by Location
I've updated my model so that I have a stores table as well:
I followed a bunch of other disucussion regarding creating cumulative totals, and backlogs, but for the most part these are talking about things like counting open tickets and don't seem to need to separate by location as well as date.
ekroll by location you mean store?
Any cummulative measure will be calculated for each store/location just by putting them on the filter.
Regarding cummulative, do you mean runnning total, or in case of a back log, the last date?
Also, I see you have some inactive relationships there. Make sure they are turned on.
I really suggest to do some reading about this. Regarding time intelligence you have a great resource here for most of the patterns including running total:
https://www.daxpatterns.com/standard-time-related-calculations/
- ekroll4 years agoFrequent Visitor
Yes, sorry, I was in the middle of adding some additional context when you replied to the first one.
So, I need to figure out cumulative backlog by store number, which is essentially:
(Any remaining pallets from previous day + 'Pallets Built'[PALLETS]) - 'Capacity'[Seasonal Capacity]I've looked at the built in time functions and standard calendar related functions don't work for me as I need to use our company financial calendar and cannot rely on standard calendar dates aligning with our company's financial dates.
The 445_Calendar table I have in my model has all of the dates down to day-date that correspond to our company financial calendar.