# Adding a constant value on a Report's TimeSeriesChart with a refresh **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision, reporting\ **Created:** [July 19, 2024, 4:14pm UTC](https://forum.inductiveautomation.com/t/adding-a-constant-value-on-a-reports-timeserieschart-with-a-refresh/93478 "2024-07-19T16:14:59Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [July 19, 2024, 5:46pm UTC](https://forum.inductiveautomation.com/t/adding-a-constant-value-on-a-reports-timeserieschart-with-a-refresh/93478/4 "2024-07-19T17:46:36Z")
I would replace the range axis with one that dynamically computed its upper/lower range from the data and any auxiliary values whenever it is asked for upper/lower. I vaguely recall doing this at one point to deal with Vision's classic chart not calling `configureChart()` after fresh data arrives. But I only found this: > [@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 … The technique for delegating range requests to other data instead of constants would be similar to that dynamic range marker. --- _[View the full topic](https://forum.inductiveautomation.com/t/adding-a-constant-value-on-a-reports-timeserieschart-with-a-refresh/93478)._