V#VarianceExplanation - Best Ways to Use
Hi,
I'm trying to understand the best way to add annotations and comments in OneStream to explain variances.
Last week at splash I was advised to use V#Annotation or V#VarianceExplanation. But w...
Forum Discussion
You can not have any annotations or other text based view members within a GetDataCell. The explanation needs valid members for each dimension. You could use V#Annotation for any comments related to the forecast amount and then V#VarianceExplanation for comments related to that scenario vs Actual. On the View member filter you can add a custom name like this V#VarianceExplanation:Name(Actuals vs AOP).
got this makes sense, so it sounds like your company just has to create some general operating rules about agreeing about what is going to be in V#varianceExplanation....
What about with calculated fields? Would that be helpful at all? Like if we created a dedicated Actuals vs AOP calculated member? and then used V#VarianceExplanation to record the explanation there? I'm not sure if that would work, but it was just a thought / idea? Still rather new here and trying to understand everything that is possible.
