Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello friends,
I have a data in cubes. When i use directquery it is displaying correct values without aggregation. If i use import query, values are aggregating like sum, count, etc....
Ex : Below picture when use directquery ,for LPC getting proper values without aggregation. (LPC in Decimals)
Ex : Below picture when use Import, for LPC getting aggregation like SUM. (LPC in Decimals). Even if change option Summarization to Don't summarize it's not working. I dont want to do sum or count. I would like to display the values like above picture.
If anuonce know plese let me know.
Thanks in advance
Solved! Go to Solution.
Hi @harib,
When you use live mode, these calculated fields still host and processed on your database side, power bi only connects and shows the result on the power bi side.
So these calculate field has been recognized correctly as calculated with raw expressions. If your expressions existed specific filters or conditions, it may not works properly on the total level, you need to add if statement with filters to trace and process the total level calculations.
Measure Totals, The Final Word
If you use the import mode, power bi will break expression and convert them to static values which support aggregate.
For this scenario, it is hard to prevent the aggregate of these fields even if you setting the data category to 'do not summarize', they will also aggregate with 'count'/'first'/'last' mode when you use on matrix value fields which only allow showing the summarized values.
Regards,
Xiaoxin Sheng
Hi @harib,
When you use live mode, these calculated fields still host and processed on your database side, power bi only connects and shows the result on the power bi side.
So these calculate field has been recognized correctly as calculated with raw expressions. If your expressions existed specific filters or conditions, it may not works properly on the total level, you need to add if statement with filters to trace and process the total level calculations.
Measure Totals, The Final Word
If you use the import mode, power bi will break expression and convert them to static values which support aggregate.
For this scenario, it is hard to prevent the aggregate of these fields even if you setting the data category to 'do not summarize', they will also aggregate with 'count'/'first'/'last' mode when you use on matrix value fields which only allow showing the summarized values.
Regards,
Xiaoxin Sheng
This is a bit of a guess but powerbi uses some intelligence behind the scenes to only offer options in the Values well that make sense.
I wonder if the model and relationships that you have are preventing 'do not summarize' from being offered because it doesn't make a difference i.e. the values would be the same in a visualisation - and this implies that the relationships in the directquery model do allow a 'do not summarize' because they would show a difference .
Perhaps you could investigate this.
What options are there from the dropdown in the Values well (the down arrow next to LPC)?
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
76 | |
74 | |
57 | |
39 | |
33 |
User | Count |
---|---|
71 | |
66 | |
57 | |
49 | |
47 |