# How to set (pass) a dynamic value for lower and upper ranges of Y-Axis in chart **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [January 8, 2025, 8:13am UTC](https://forum.inductiveautomation.com/t/how-to-set-pass-a-dynamic-value-for-lower-and-upper-ranges-of-y-axis-in-chart/100570 "2025-01-08T08:13:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 8, 2025, 1:24pm UTC](https://forum.inductiveautomation.com/t/how-to-set-pass-a-dynamic-value-for-lower-and-upper-ranges-of-y-axis-in-chart/100570/2 "2025-01-08T13:24:36Z")
The Classic Chart component doesn't run `configureChart` for data changes. The proper solution is to use customized `ValueMarker` instances that look at your custom props every time they are asked for their value, and to replace the range axis with a custom Axis that does similar with your bounds. See this topic for inspiration: > [@Change background color of vision chart](https://forum.inductiveautomation.com/t/change-background-color-of-vision-chart/73322/8): > > Sure. I have this in a chart\_util library script: from org.jfree.chart.plot import ValueMarker from java.awt import Color, BasicStroke # # Supply a function to obtain the range value to mark with the given # color and stroke. class DynValueMarker(ValueMarker): def \_\_init\_\_(self, callable, clr, stroke): super(ValueMarker, self).\_\_init\_\_(0.0, clr, stroke) self.callable = callable def getValue(self): return self.callable() You apply the above in configureChart with a function that reads … --- _[View the full topic](https://forum.inductiveautomation.com/t/how-to-set-pass-a-dynamic-value-for-lower-and-upper-ranges-of-y-axis-in-chart/100570)._