Forum Discussion
Variances between columns
Ok so that tells me that for each ForecastMonth, the First and Last Date are coming back with the same date. On the brightside, that suggests that the formula overall is working. Its now a matter of understanding why, on a row by row context, we are only seeing a single Submission Month date.
I feel like you can by using ALLSELECTED and potentially using another variable to remember the forecast month row context which i'm expecting will be lost when ALLSELECTED is used.
To make use of ALLSELECTED, it would look something like:
LastForecast = CALCULATE(
sum('DPLImportPBI'[Forecast Revenue]),
ALLSELECTED('DPLImportPBI'),
'DPLImportPBI'[SubmissionType] = "Rolling Forecast",
'DPLImportPBI'[Submission Month] = EndDate
) I'm expecting if you use the above as is, your forecast month row context could be lost. If thats the case, just add a new variable in your formula with LASTDATE and that column, then put it into the calculate formula as another filter condition along with the 3 in the above.
Sorry this doesn't achieve what I'm looking for and maybe I didn't explain correctly.
For started the ALLSELECTED option pulls in all revenuve for all forecasts and I definitley do not want that.
The main issue I have it that the matrix visual has a 2 tiered colum heading. It has July 2017 and November 2017 (becasue these are the 2 submission months I have chosen in my slicer. Below these are the column headers for my measues (RF Revenue, RF EBIT & RF Margin).
When I add the varaince measures it tries to give a variance for the July forecast and also a varaince for the November forecast. I do not want this... I want one varaince comparing the 2 forecast. This works perfectly ok as a seperate visual but not if I try and add it to the existing visual
ALLSELECTED is likely the avenue you'll need to persist with, but it won't be enough on its own. As you have correctly pointed out, it will strip extra context away. You can first record this context into additional variables and add back into your calculate statement. It will just simply take some trial and error for you to get right.
Really comes down to the choice of whether the 2 visuals are going to be enough or whether you wish to spend the time and effort in adding additional complexity in order to squeeze it into the single visual. Its a bit hard to solve from afar so its one of those problems you will need to pick up and run with.