Forum Discussion

Mark1982's avatar
Mark1982
Icon for Helper I rankHelper I
5 years ago
Solved

Weird results in graph

Hi,

 

I've been building many Power BI dashboards and reports on vairous different data sources. This time i am experiencing an issue which has me baffled.

 

The scenario is simple. One SQL Table source which contains around 3000 records. The data is finance data and should balance out. In essence this means calculating monthly should balance to 0. The data comes in as decimal data with 2 decimal spaces (1.2). When using the amount field within a table it diaplys the correct output, same applies to a created measure 

Amount Test = CALCULATE(SUM(GenLedgerEntries[Amount])).
 
But when putting this in to a graph the output is totally messed up. Again I am baffeld. Anyone expereinced this before?
 
Need Help
  • Mark1982's avatar
    Mark1982
    5 years ago

    Right,

     

    My last reply has led me to dig deeper into the decimal spacing. Clearly i am facing an overflow issue within the graph output. When tranforming the amount field to fixed decimal resolves the issue. The SQL column amount is set to decimal 38,20 whilst Power BI decimal "number of significant digits is limited to 17 decimal digits". This clearly conflicts. I am stunned that this only seems to overflow on the graph. That has send me in the wrong direction.

     

    Seems like I just created a nice knowledge base topic for the community :).

3 Replies

  • mahoneypat's avatar
    mahoneypat
    Icon for Microsoft Employee rankMicrosoft Employee
    5 years ago

    In your table visual, you have both the year and month columns.  In your line chart, you have just the month, so your multiple years are combined.  If you also add the year to your visual, you should get the expected result.

     

    Regards,

    Pat

     

  • Mark1982's avatar
    Mark1982
    Icon for Helper I rankHelper I
    5 years ago

    Unfortunately no valuable input as yet. Did some more playing around and have simplified my dataset even more to see how this affects the output. See attached image. Really do not understand where this is coming from. The graph is going bonkers. Do you guys think i should raise this as support issue with MS?

  • Mark1982's avatar
    Mark1982
    Icon for Helper I rankHelper I
    5 years ago

    Right,

     

    My last reply has led me to dig deeper into the decimal spacing. Clearly i am facing an overflow issue within the graph output. When tranforming the amount field to fixed decimal resolves the issue. The SQL column amount is set to decimal 38,20 whilst Power BI decimal "number of significant digits is limited to 17 decimal digits". This clearly conflicts. I am stunned that this only seems to overflow on the graph. That has send me in the wrong direction.

     

    Seems like I just created a nice knowledge base topic for the community :).