You can try to use Version (Dimension) instead of Scenario to create a calculated item for the difference between two items under dimension Version.

. 

Hi Min Lee - we did not opt to use a Versions dimension and instead chose to run all BVAs and comparisons through Scenarios, so inserting this dimension would cause a lot of downstream impacts and refactoring in our model. Wondering if a workaround exists for this given that we did not build using Versions

Hey Chris, here’s a hacky workaround:
1. Create a duplicate metric in the security folder (or another application without scenarios). This forces that metric to always be selected on the Current Forecast scenario
2. Create a variance metric = ‘Original Metric’ - ‘Duplicate Metric in the Security Folder’. Page select on your Plan Scenario, and you can now chart just this variance metric.

The limitation of this workaround is you are always comparing against the Current Forecast scenario (but this is often the case anyways).

Hi ​@gablahoz ,

That’s a really nice workaround !
I forgot the Security Folder couldn’t handle scenario so it “forces” metric to select the Default/Current Forecast Scenario.
However, as you mentioned, it will always compare against Current Forecast Scenario, but that’s the only caveat, and not too constraining. 
Thanks for the tips

Agreed with ​@CDALMAY this is a good workaround! Thanks ​@gablahoz !