IBM Apptio

Apptio

A place for Apptio product users to learn, connect, share and grow together.


#Aspera
#Apptio
#Automation
#FinOps
#Apptio
#ITAutomation
 View Only
  • 1.  Forecast Metric

    Posted 04/15/16 10:10 AM

    We created a metric using the following formula that overrides forecast with cost for months that have a cost. (=If(LookupObjectTotalValue(Cost Source,Cost)>0,Cost,Forecast)) Then, I also created a metric to get the FY Forecast using (=Annual(Forecast BTS)). These are both working fine in reports for each individual model object.

    However, when we try to report on 2 objects, it zeroes out the FY metric. For example, we have a report for our business units that lists the Cost, Budget, and Forecast by Business Service that we slice by their Business Unit. Both the new Forecast and FY Forecast columns show up fine until I choose a Business Unit in the slicer, and then the Forecast column is fine, but the FY Forecast column zeroes out. This happens whether I use the FY metric I created or change the value setting of the regular monthly forecast to FY. Any ideas?




    #CostingStandard(CT-Foundation)


  • 2.  Re: Forecast Metric

    Posted 04/15/16 12:20 PM

    @Elizabeth Lewis,

     

    Not sure if this will help or not without seeing the report, but is the Business Unit slicer locked as a perspective to the Business Unit Allocation Table?

     

    Also, another way of potentially testing this could be pulling in all of the metrics and create potentially a tree map where you would pull in the Business Unit and then the Business Service column.  Then you could pull in all the metrics and still potentially add the slicer if you needed too.


    #CostingStandard(CT-Foundation)


  • 3.  Re: Forecast Metric

    Posted 04/19/16 02:14 PM

    Another thing you could try is creating a formula coloumn on the report (=Annual(Forecast)) and publishing the new coloumn to a perspective instead of using the metric. This way, you can publish the new formula coloumn to a perspective and lock it to the same object that your slicer is locked to. Does this make sense?


    #CostingStandard(CT-Foundation)


  • 4.  Re: Forecast Metric

    Posted 04/20/16 09:29 AM

    Agreed. Adding a new custom column to the report table is a good option here, using the same formula as the calculated metric.

     

    Calculated metrics (as opposed to modeled metrics) only have a value when seen through the lens of a single object in a model.

     

    When you lock a report table to two objects instead of one, calculated metrics will no longer show up, or you'll receive a warning: "Please provide a row or column to cross reference Object A and Object B."


    #CostingStandard(CT-Foundation)