Forum Discussion

Croftie's avatar
Croftie
Advocate I
8 years ago

Line chart truncation

Line charts appear truncated at the top when a minimum value of zero is set for the y-axis as per the example below.

I suspect this is a Power BI bug given the number of posts about chart truncation. The x-axis is categorical (as required to produce a line chart with markers), and making it continuous makes no difference to the truncation of y-axis labels.

Any advice would be greatly appreciated.

Steve

12 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Croftie,

    I can't reproduce your issue in the latest version of Power BI Desktop, you can review the example in my scenario. Do you use August version of Power BI Desktop(2.49.4831.521)? 



    Regards,
    Lydia Zhang

    • Croftie's avatar
      Croftie
      Advocate I
      8 years ago

      Yes - it is the August version. Can you try it with markers? Not that mine works without markers.

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        Croftie,

        Everything works well even turn on markers. You can review my PBIX file. Would you mind sharing me your PBIX file?



        Regards,
        Lydia

    • VidaLi's avatar
      VidaLi
      Frequent Visitor
      8 years ago

      Hi Lydia, 

       

      i am experience the same issue as Steve did. the reason why you couldn't replicate it, is because your max is big enough, so the line chart is not at the top of the edge, but it doesn't solve the issue though,

       

      cheers,

      Vida

  • VidaLi's avatar
    VidaLi
    Frequent Visitor
    8 years ago

    I am experiencing the same issue as mentioned by Steve. Hopefully someone knows how to fix this or is it a bug needs to be fixed by Microsoft?

     

    cheers,

    Vida

  • VidaLi's avatar
    VidaLi
    Frequent Visitor
    8 years ago

    hi chass Charles,

     

    I am hoping to get you attention. I definitely think this is a bug as Croftie raised in his original post. I am wondering if PBIX is going to fix this bug in the nearest release?

     

    cheers,

    Vida

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Croftie VidaLi,

    I will report this issue internally and post back once I get updates.

    Regards,
    Lydia

    • VidaLi's avatar
      VidaLi
      Frequent Visitor
      8 years ago

      Thank you Lydia. Looking forward to Microsoft's update about this.

      • v-haibl-msft's avatar
        v-haibl-msft
        Microsoft Employee
        8 years ago

        VidaLi Croftie

         

        I’ve got response from the Product Team.

         

        This is by design currently. Once users set a min or max axis value, we use a combination of the specified values and/or the actual values where the user has not defined a value. So, once you set the Min, we change logic. Max is undefined so we use the real max of 19,418 as the top. Dropping the last label is by design to there is minimal whitespace and so we respect what the user has specified. This is the same as if the user had typed in 19,418 as the Max - they wouldn't want us to jump to 20k on the axis just to label the top.

        All that said, we have discussed a plan to expose part of this behavior to the user as an option. The axis ticks can be rounded "nicely" to include the next label based on the tick interval - which would show 20k in this case. We will leave defaults as-is so existing visuals aren't affected, but we plan to introduce a new toggle to control whether the axis should extend to the next tick interval outside the domain or not.

        No ETA right now, hopefully by end of this year.

         

        Best Regards,
        Herbert