Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

A Simple Calculated Column With IF Statement

I'm having a really hard time with a seemingly simple calculated column.  I have a table representing route data with rows/values indicating picks, drops, lunches, leave base, return base, etc.  There are multiple routes with multiple activities on each route.  I just need a column evaluating every row and indicating whether the activity is a pick, so I tried the following:

 

ISPick = IF(
    'Manifest'[Activity] = "Pick", 1,0
    )

I'm expecting a 1 in the column if the row is actually a pick (vs any other type of activity) otherwise a 0.

 

 

I'm getting an error "A single value for column 'Activity' in table 'Manifest' cannot be determined.  This can happen when a measure formula refers to a column refers to a column that contains many values without specifying an aggregation such as min, max, count, or sum to get a single result."

 

I'm so confused. It seemed like the logic was so basic to get this done.  What did I miss??

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Sounds like you are adding a measure and not a calculated column.  They look the same, but act very differently:

  • Hi,

     

    There is no mistake in your formula.  I think you are writing that as a measure.  It should be written as a calculated column formula instead.

  • v-yulgu-msft's avatar
    v-yulgu-msft
    Microsoft Employee

    Hi Anonymous,

     

    As Ashish_Mathur and Nick_M suggested, you should make sure you created a calcuated column rather than a measure with above formula. If you want to new a measure to evaluate every row and indicating whether the activity is a pick, you need this formula:

    ISPick = IF( SELECTEDVALUE('Manifest'[Activity]) = "Pick", 1,0 )

    Best regards,

    Yuliana Gu

    • Anonymous's avatar
      Anonymous
      Not applicable

      All,

       

      I'm definitely using a calculated column and NOT a measure so still not sure why this is happening.

       

      Since I can't get beyond this, I think I'll have to approach things differently and just create the field directly from the datasource rather than create it in the power bi model.

       

      Thanks

      • Anonymous's avatar
        Anonymous
        Not applicable

        if you can upload a sample I can take a look.  Should be relatively straight-forward.