Nice job explaining the problem and providing all the relevant information. That definitely makes it easier for us to provide quality support and solutions.
See how this works for you:
The key is building the measures off the date slicer using a disconnected date table, rather than the primary date table within the model.
The HarvestMin and HarvestMax measures are just the standard date slicer harvest pattern. Calculating the beginning of the fiscal year based on HarvestMin is a little more complex:
Harvest Start of FY Date =
VAR _SelDate = [Harvest MinDate]
VAR _SelFY =
LOOKUPVALUE( 'Date'[Fiscal Year], 'Date'[Date], _SelDate )
VAR _Result =
CALCULATE(
MIN( 'Date'[Date] ),
FILTER(
ALL( 'Date'[Date], 'Date'[Fiscal Year] ),
'Date'[Fiscal Year] = _SelFY
)
)
RETURN
_Result
Then from there, it’s just calculating total sales over the two different date ranges defined by the slicer:
Hi @ibesmond, did the response provided by @BrianJ help you solve your query? If not, how far did you get and what kind of help you need further? If yes, kindly mark as solution the answer that solved your query. Thanks!
@BrianJ
Looks to be working in my model. Still in the validation stage, but so far ties out perfectly. Thank you for your response. The disconnected date table was a challenge and forced me to have to modify all my current measures to get them to react to the disconnected table.
I had to create an inactive relationship between the disconnected date table and my original date table and then utilize the USERELATIONSHIP function to align my measures with the disconnected date slicer when it was appropriate. Now I feel like I am an expert when it comes to the function, which is all thanks to your support answering my question. Thanks again!