Hello,
I have a reactive application using the line chart widget:
The line chart x-axis value is reflecting the incorrect value for the "flank" and "root" line. Its x-axis value is somehow taking the x-axis value of the "cutoff" line for some reason. Any suggestions on this? Thank you!
Hi everyone!
I'm cross-posting here some of the finds I got in this topic.
Original post: https://www.outsystems.com/forums/discussion/97298/outsystems-chart-stacked-bar-bug/#Post421537
----
I looked into this, and looks like the xAxis "ValuesType" is wrongly set (possibly using the default value).
If you change the xAxis property "ValuesType" to "Category":
And that should display the data in the correct way:
If you have any question let me know.
Cheers,
RG
Just to add on, I created another new application just to test out the line chart widget:
Some how the "cutoff" graph is showing the wrong x-axis value. Very confused as to what is causing this
any suggestions on this?
no, it's too hard to guess what you are exactly doing.
please share the oml with the actual data you are using, demonstrating the problems.
It might be related to sorting of the aggregate, it might be a data type problem, but I'd have to test out your oml
Hello, attached is my oml for the second line chart
Hi @Low Nico ,
As far as I can tell, this is a bug in version 3 of the chart.
It think the component makes up the labels at the bottom only looking at part of the data, and works under the assumption that each series will have the same set of labels in the same sequence.
As far as I am concerned, this is a false assumption, it should be possible to plot charts where for some series, some labels do not have a value, and all labels should be visible, not just those of the first series that comes along.
I already reported this as a problem in the post announcing the 3.0 charts version in the beginning of may. It was a column chart there, but I think it is the same problem here. They said the fix would be included in the next release.
For a line chart, I don't really see a workaround, in a column chart, I think something could probably be done with 'invisible' data points to fill in the holes.
Dorine
So, stick to v1 chart until this is solved
Hello Dorine,
Thank you for your help on this and your clarification. I reverted back and used the v1 line chart as you suggested and it is working as intended.