Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

Change to View manipulation in TI processes after v2.0.9.3

  • 1.  Change to View manipulation in TI processes after v2.0.9.3

    Posted Wed May 26, 2021 09:47 PM
    Hey everyone,
    I have a super specific issue affecting view manipulation in TI processes. I get different results in PROD v2.0.9.3 and DEV v2.0.9.7.

    Here's the scenario:
    Cell 1 - has a numeric value input (let's say 100)
    Rule on Cell 1 - forces value of Cell 1 to 0 (after updating a month parameter)
    We do this to zero out forecast values for closed periods through rules based on a forecast month parameter.

    Cell 2 - has calculated measure (let's say 50%)

    I want my view extract to exclude zeroes (including zeroes due to a rule - like Cell 1)
    I want my view extract to exclude rule-calculated measures (Cell 2)


    In PROD v2.0.9.3, the settings below give me the desired outcome. It appears that it might be due to separate passes on the data that are applied sequentially. First, the zeroes are filtered out (including any zero values due to rules). Then, the remaining values from rules are skipped. We've been using this logic for years without issue.

    ViewExtractSkipZeroesSet (Cube, View, 1);
    ViewExtractSkipRuleValuesSet (Cube, View, 1);

    In DEV v2.0.9.7, the same settings produce a different outcome. Since rules are skipped, Cell 1 has a value of 100 instead of 0 and is included in the extract (which I don't want). It appears that in the newer version each setting is applied independent of each other...which makes sense to me, but I couldn't find any documentation on the change anywhere. Maybe we were taking advantage of a loophole that was closed??

    If anyone has seen this and can confirm, that would be super helpful. If not, please watch out for this in your own TI scripts. We have had to comb through all our scripts and make changes and were definitely caught off-guard.
    Thanks,
    Kirk

    ------------------------------
    Kirk Stolworthy
    ------------------------------

    #PlanningAnalyticswithWatson