[Vishwas R]

@juliecooling1,

Glad that helped you out :)

—
Vishwas R
Team CanvasJS

[Vishwas R]

@juliecooling1,

Yes, it’s possible to arrange slices of pie from smallest to largest by sorting dataPoints in ascending order before rendering the chart. Please take a look at this JSFiddle.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@shreekanthb28,

Incase of area charts, dataPoint y-values start from 0 – because of which the color of dataseries overlaps. Based on the example that you have shared, i would suggest you to use Stacked Area Chart.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@ayanghatak,

Thanks for bringing it to our notice. We will check if there is any issue in the default value for smaller height of the chart and update accordingly.

—
Vishwas R
Team CanvasJS

[Vishwas R]

Omry,

Updating dataPoints on rangeChanging event seems to be working fine. Please take a look at this JSFiddle which shows filtering dataPoints based on zoom-level.

If you are still facing the issue kindly share JSFiddle that reproduces the issue you are facing, so that we can look into code, understand the scenario and help you out.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@lokey2094,

Sorry it’s not possible to have 12 divisions (7.1, 7.2, 7.3… 7.11) between 2integers (7 & 8) as axis scale between two integers are divided into 10 fractions (7.1, 7.2, 7.3,… 7.9).

The JSFiddle that you have shared doesn’t have the data 7.1, 7.11, etc which you are referring. Kindly share JSFiddle along with sample data and brief us according to the sample data so that we can understand it better and help you with the possible solution.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@nazrime,

Please take a look at this JSFiddle.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@ady-shaputra,

It seems to be exporting along with the chart legend.

If you are still facing the issue, kindly create JSFiddle reproducing the issue you are facing and share it with us so that we can look into it and help you resolve.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@ayanghatak,

The minimum width of the dataPoint seems to become negligible when the height of the chart is 180px. Setting dataPointMinWidth to 1 seems to be working fine. Please take a look at this updated JSFiddle.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@lokey2094,

Please take a look at this updated JSFiddle.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@sean_wdl,

Using the code snippet shared above we are unable to reproduce the issue at our end. Can you kindly create a JSFiddle reproducing the issue you are facing and share it with us along with the sample data so that we can look into the code and chart-options being used by you to understand the scenario better and help you out?

From what we have observed, sometimes things get delayed mostly when we are not able to reproduce the issue or not able to understand the exact requirements or the solution that we provide may not work properly due to the variation in chart-options being used by you and us.

Having a JSFiddle helps us in figuring out the issue and suggesting an appropriate solution accordingly.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@andenjs,

For one thing, I apparently need to append “000” to Unix timestamps? Otherwise, they are wrong. Is that right?

Unix Timestamp is the number of seconds that has elapsed since January 1, 1970 whereas JavaScript timestamp is the number of milliseconds that has elapsed since January 1, 1970. Multiplying unix timestamp by 1000 gives you JavaScript timestamp.

Second, the example I was looking at has the X-axis format under data. However, this doesn’t work

xValueFormatString is used to define the the format of x-value that appears in toolTip and indexLabel whereas valueFormatString is used to define the format of the value that appears in axis. Setting valueFormatString should work fine in your case.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@lokey2094,

Crosshair label is showing 7.1 due to it’s valueFormatString (which might be #,###.# or #,###.0). Changing valueFormatString to “#,###.00” should work fine in your case.

In order to help us in understanding the issue, please have a reproducible demo of your chart.

This one step can assure you a speedy response. Fork out our template JSFiddle and reproduce the chart at your end. Try to keep it to the bare minimum by removing unnecessary code.

From what we have observed, sometimes things get delayed mostly when we are not able to reproduce the issue or not able to understand the exact requirements or the solution that we provide may not work properly due to the variation in chart-options being used by you and us.

Having a JSFiddle helps us in figuring out the issue and many a times we can just edit your code on JSFiddle to fix the issue right-away.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@munmun,

The sample shared by @manoj-mohan seems to be working fine. If you are still facing issue, kindly create sample project reproducing the issue and share it over Google Drive or Onedrive, along with sample database, so that we can run it locally at our end, understand the scenario better and help you out.

—
Vishwas R
Team CanvasJS

[Vishwas R]

@munmun,

Please take a look at this sample project for multiseries chart in JSP with datapoints being fetched from oracle database. You can use zooming / panning feature when there are more number of datapoints for better visualization, please refer documentation for more information.

—
Vishwas R
Team CanvasJS