Forum Discussion
What determines which numeric fields get Aggregates?
I have a table with three numeric fields. They are Price, Cost, and Profit in the figure below.
All three defaulted to Do Not Summarize in the Data view. Thus, they do not appear as an Aggregate field in Report View. What causes Desktop to make this determination? Since this is essentially a Dimension table for this model, I am pretty happy abou this decision. I just want to understand what drove Desktop to make this choice.
Interesting. Just to keep the conversation alive, I observe the following.
Load the text file - I see that price and cost default to "Sum"
Add another (fact) table and a relationship is automatically determined between the 2 tables (BarID)
The aggregates of Price and Cost automatically changed to "Do Not Summarize"
So, based on my testing I would say that initial loads of all data default to an aggregate, unless a relationship is detected/applied that will drive a 1 to many relationship, and thus change the default behavoir based on a fact/dimension relationship...
It would be good to hear an official answer, but that is what I'm seeing.
4 Replies
I'd be interested in what you pulled the data in from. I just tested all the ways I can think of from excel and it imported the whole number and currency formatted values in and automatically set them to default them to "Sum". My initial guess is that there is some formatting that is being done in your source that Power BI recognizes/doesn't recognize...
The sources is a simple text file.
"BarID","Flavor","Size","Price","Cost"
1,"Milk Chocolate","Small","1","0.4"
2,"Dark Chocolate","Small","1","0.4"
3,"Caramel","Small","1","0.4"
4,"Crisp","Small","1","0.4"
5,"Milk Chocolate","Large","2","0.8"
6,"Dark Chocolate","Large","2","0.8"
7,"Caramel","Large","2","0.8"
8,"Crisp","Large","2","0.8"Interesting. Just to keep the conversation alive, I observe the following.
Load the text file - I see that price and cost default to "Sum"
Add another (fact) table and a relationship is automatically determined between the 2 tables (BarID)
The aggregates of Price and Cost automatically changed to "Do Not Summarize"
So, based on my testing I would say that initial loads of all data default to an aggregate, unless a relationship is detected/applied that will drive a 1 to many relationship, and thus change the default behavoir based on a fact/dimension relationship...
It would be good to hear an official answer, but that is what I'm seeing.
