RichardRayJH
New Member
- Joined
- Jan 18, 2013
- Messages
- 24
I work for a winter resort (Jackson Hole, Ski Resort, Skiing, Snowboarding, Vacation Packages and Ski Trips | Jackson Hole Mountain Resort | Jackson Hole Mountain Resort | Jackson, Wyoming). Like most winter resorts our operating season spans the normal calendar year; it normally runs from a date in the last half of November to one in the middle of April of the following year. Opening and Closing dates are determined by a day of the week: we always open on a Saturday in November and close on a Sunday in April, but it might be any of the Nth such days in the month. I have a table (Season Dates) with each season's Opening and Closing Dates, as well as dates for holidays like MLK Day, Presidents Day and Easter that move around each year.
All Year To Date (YTD) calculations of interest are actually Season To Date (STD). The standard date functions in PowerPivot for YTD, etc. seem pretty useless for my needs. Can anyone suggest a generalized approach to this problem?
For instance: I have a Net Revenue column with daily net by date. How do I calculate a STD sum for a date range beginning on Saturday, 11/28/2013 running through Sunday 4/6/2014? And, do it again for Saturday, 11/24/2012 through Sunday, 4/7/2013. Etc, etc., back through the seasons?
What I'd like, I think, would be a way to create a surrogate for the built in YTD functions to which I could feed my own definitions of the start and end dates. Does that make sense? Another approach?
TIA
All Year To Date (YTD) calculations of interest are actually Season To Date (STD). The standard date functions in PowerPivot for YTD, etc. seem pretty useless for my needs. Can anyone suggest a generalized approach to this problem?
For instance: I have a Net Revenue column with daily net by date. How do I calculate a STD sum for a date range beginning on Saturday, 11/28/2013 running through Sunday 4/6/2014? And, do it again for Saturday, 11/24/2012 through Sunday, 4/7/2013. Etc, etc., back through the seasons?
What I'd like, I think, would be a way to create a surrogate for the built in YTD functions to which I could feed my own definitions of the start and end dates. Does that make sense? Another approach?
TIA