Flexchart: How to set default Min value for Y axis

Posted by: nilesh_nichal on 16 December 2018, 9:14 pm EST

  • Posted 16 December 2018, 9:14 pm EST

    Hi,

    I am facing an issue with setting the min value on Y -axis of flexChart.

    I am using following code as per documentation to set value but it’s not working.

    this.linechart.axisY.min = 0;

    Could you please help on this asap.

    Thanks

  • Posted 16 December 2018, 10:48 pm EST

    Could you let us know the exact issue you are facing and the Wijmo version?

    We tried to set min value and it seems to be working fine.

    We used the following sample for testing: https://stackblitz.com/edit/angular-1kfyvj?file=app%2Fapp.component.ts

    Please have a look at the above sample and let us know if are missing something to replicate the issue?

    ~Sharad

  • Posted 17 December 2018, 9:18 pm EST - Updated 3 October 2022, 9:47 am EST

    Hi Sharad,

    Thanks for your quick response.

    The Y axis shows the values in negative format like -0.5,-0.4,-0.3 when the graph point values are equal to 0. Please find attached image with changes in the template which you already shared.

    I want to show the graph as normal starting with 0, When I don’t have any data to show on graph.

  • Posted 17 December 2018, 9:55 pm EST

    In such a case, please set both min as well as max properties of the y-axis and that should fix the issue.

    You may refer to the following updated sample for reference: https://stackblitz.com/edit/angular-tnv9xb?file=app%2Fapp.component.ts

  • Posted 26 December 2018, 8:20 pm EST - Updated 3 October 2022, 9:47 am EST

    Hi Sharad,

    I tried the above code , it works for 0 values, but when I get data from the API for the points and values are greater than 1 then I am not able to see the graph points. I have attached an image to understand the scenario

    PFA:

    Provide solution to start the Y-axis always form 0 , whether the data for graph points is 0 or more.

    Thanks.

  • Posted 27 December 2018, 10:02 pm EST

    Hi,

    We are able to replicate the issue and hence forwarded it to the devTeam for further investigation(Internal tracking Id: 359892). We will let you know as we get an update on this.

    Regards

  • Posted 27 January 2019, 5:20 pm EST

    Hi,

    Could you please provide update on this Issue. As we are stuck on this point for development.

  • Posted 28 January 2019, 6:06 pm EST

    Hi Nilesh,

    The issue is still with the dev team. We have asked the team for an update and will let you know as we get an update on the issue.

    Sorry for the inconvenience caused due to the delay.

    Regards

  • Posted 18 November 2019, 9:18 pm EST

    Hi Nilesh,

    This issue has been verified as fixed in the latest release build 5.20193.637.

    Please check at your end.

    Regards,

    Manish Gupta

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels