Forum Discussion
Value are not the same between table and graph
Hello all,
I am encountering an issue with my figures between table and graph representation...
As example, on my table, I have these value :
And within a graph I have the following :
On my example June : 47 on table (which is the good one value) vs 70,32 on a graph...
Do you have any idea ?
For more information, on my table I have following agregation setting :
Whereas on the graph I have this one :
One assumption is that is 'simply' due to the agregate rule.
But.... there is no way to change it or to set as 'No agregate' on the graph.
Thank you so much in advance.
Regards
Hi gaetangoumaz
Unfortunately, I can't assist at this stage because I still don’t fully understand your data structure and what you are trying to accomplish. The most I can do is share a dummy file I use for demonstrating solutions. You can try to create something similar to what you need in that file, including the desired result.
If you manage to do so, please save it in a public cloud service and share it via an open link.
6 Replies
Hi gaetangoumaz
The difference in values between your table and graph is likely due to how aggregation is applied. Based on your images, it seems the table uses a single layer of data, whereas the graph appears to have a hierarchy. This difference means that aggregation behaves differently because the context changes, causing discrepancies.
Graphs in Power BI always require some form of aggregation (like a pivot table in Excel), even when tables can show individual values without it. This is why you're seeing different numbers; the graph aggregates based on the hierarchical context, which doesn’t match the table.
To better assist with resolving the issue, it would be helpful to see the PBIX file in English with the data structure you're working with, along with a clear example of the desired outcome. I recommend creating a dummy version of your report (without sensitive data), saving it on a public cloud service (like OneDrive, Google Drive, or Dropbox), and sharing a link. This will make it easier to understand the exact problem and provide more specific guidance.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi gaetangoumaz ,
Your idea is correct because different aggregations make different values displayed in the visual object and if you select the same aggregation then they will also display the same values.
In a table, you can choose not to aggregate because it displays the same categories over and over again, as you can see in the following two images.Whereas in Line Chart, there will be only one point for the same classification, so there is no option of not aggregating.
Therefore, you can choose the appropriate aggregation in line charts or by creating your own measure or calculated columns to show the desired results.If your Current Period does not refer to this, please clarify in a follow-up reply.
Best Regards,
Clara Gong
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Anonymous and Ritaf1983
Thank you to both of you for your answers
Yes I think unfortunately a dedicated column or calculated column has to be created...
I still does not understand why Power BI can not apply the agregation on the axis mentioned. In my case this in simply city and date.
Is it a bug to raise to Microsoft or is not 'normal' such behaviour ? For me, who use other tools such as SAP BI, Cognos, etc, this is surprising.
Actually, understanding your answer, it means I should create a column (or measure ?) having which syntax ?
Is is calculate, averagex ?
I must admit being a little bit lost.
Thanks in advance.
Best regards,
Gaetan
Hi gaetangoumaz
This is not a bug; it's the logic of how the engine works. I can understand the confusion between when to apply aggregation to the graph, when to use a calculated column, and when to use a measure. It's important to fully understand the tool to "swim" through it with ease.
For your current needs, I'd be happy to try and help, but I need to better understand the data you have and what you're trying to achieve. This is why I recommended creating a small dummy version of your report (without sensitive data), saving it on a public cloud service (like OneDrive, Google Drive, or Dropbox), and sharing a link. This will make it easier to understand the exact problem and provide more specific guidance.
Hi gaetangoumaz
Unfortunately, I can't assist at this stage because I still don’t fully understand your data structure and what you are trying to accomplish. The most I can do is share a dummy file I use for demonstrating solutions. You can try to create something similar to what you need in that file, including the desired result.
If you manage to do so, please save it in a public cloud service and share it via an open link.
