Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

IF statement - problem - need at row level and not calculated column

Hello I need to figure out how to get an If statement to work at the row level (iteration per row).  It cannot be a calculated column, it needs to be a measure. The simple if statement (that does n...
  • Anonymous's avatar
    Anonymous
    8 years ago

    Thank you very much.  It is so obvious now LOL  It is very time consuming to learn this through you tube so I greatly appreciate the help

Seward12533's avatar
Seward12533
Icon for Solution Sage rankSolution Sage
8 years ago

First best practice is to sue DIVIDE function rather than arithmatic /  but that is not your problem. Why you can't share actual data you shoudl be able to show snip of the table layout and relatship map and at least table layouts. Ideally you could make up some quick dummy tables with a few rows of dummy data and share that. Some idea of Actual vs Expected results may help as you may just have a fulter context / relationship issue.

 

Why is it incorrected to aggregate a SUM? I agree its not cool to aggregte individual percentags (but you can get around that with aggregated sums and counts. Sounds to me that you might be overcomplicating the model.  I have very complex Sales history reprots with attributes but Budget, Forecast and Actual and have no problem doing Montly, YTD, QTD, YOY, Variances etc.. without ever using SUMX to iterate on rows.

 

But short answer is if you need row level iteration you will need to use SUMX but a calcualated column that you can use to filter out rows easily may make some of your measures easier and potentially avoid using SUMX vs SUM.