Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago

Summarization NOT WORKING

I have a table with values from a SQL Database. I want the columns to Sum the values. I have SUM selected in the Summarization but the sigma does not show up and I can't build visualizations. 

 

 

7 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    HI Anonymous 

     

    You have to chage the data type to whole number ot integer.

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      No that's not it. I get options for latitude and longitude. I changed both to Whole number and I got an option for a bar code or postal code.

       

       

       

    • Anonymous's avatar
      Anonymous
      Not applicable

      I have a similar report that I copied some queries from where the summarizations are working without a Data Category.

       

      • Anonymous's avatar
        Anonymous
        Not applicable

        HI Anonymous ,

         

         

        Go to model View and change the Default Summarization.

         

        Also, check for the Data Type in Power Query.

         

         

         

        Regards,
        Harsh Nathani
        Did I answer your question? Mark my post as a solution! Appreciate with a Kudos!! (Click the Thumbs Up Button)

  • v-xicai's avatar
    v-xicai
    Community Support

    Hi,

     

    You may create calculated column or measure like DAX below.

     

    SumTotal_Column = SUM('Table1'[Column2])
    
    
    
    SumTotal_Measure = CALCULATE(SUM(Table1[Column2]), ALL(Table1))

     

     

     

     

     

     

    Best Regards,

    Amy 

     

    Community Support Team _ Amy

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Hello,

    the sigma is also not showing up for me in fabric, on a semantic model. It was there some days ago, but now it is gone. Has anybody any news on this issue?

     

    thx.

  • Hey, did you checked maybe for this config on the semantic model level? This solved our issue, the origin why it happend was a previously created calculation group.