Flexible configuration of X and Y axes in analytics

I am using TULIP to create graphs, but is it possible to freely change the number of digits displayed on the Y-axis?
In the attached graph, the values are rounded to three decimal places, which makes comparisons visually difficult.
It would be great if we could freely adjust the number of digits.
If you have any suggestions, please share them.

One additional point I would like to confirm is the adjustment of the X-axis range.
For the Y-axis, there are options for Fixed Maximum Bound and Fixed Minimum Bound, but these options are not available for the X-axis. As shown in the attached image, the values on the X-axis are not evenly spaced, which makes the chart very difficult to understand.

image

Hi @da-noguchi,

On the right hand side under the data tab, under “…” menu, there is number formatting feature, which you can use to increase the decimal places.

Fixed Maximum Bound and Fixed Minimum Bound on the X-axis is a gap we are aware of, and visualizations can get confusing when dealing with a large range of values. Thanks for bringing this up again, and to help us prioritize this fix against other items on our roadmap, please ‘Like’ this post so we can track the demand!

Hello @canaalpaslan ,

Thank you for response.

Even if I change that setting, it doesn’t seem to be reflected. Is there any additional configuration required?

Also, sorry if this is a bit unclear, but I have a question about the X‑axis Fixed Maximum Bound and Fixed Minimum Bound, and one more thing.

If you look closely at the values displayed on the X‑axis, you’ll notice that they are not shown at equal intervals—for example, −170, −175, −215, −220. In Excel and similar tools, these values are automatically displayed at evenly spaced intervals. I would like to have this functionality as well.

Hi @da-noguchi,

Below results are query results, therefore any visualization will not change them. Number formatting only affects the visualization of data. So that is the expected behavior.

Thanks for the feature request- we noted that on our end as well!

Best,
Cana