"Point Values Limited To 5001"

---

Hello All,,
(Mango 3.3.0 latest updates, Linux server)
I have a several data points that record temperatures at 1 minute intervals. That is 1440 readings per day per channel. I need to compare the charts of 2 channels for the entire week. When I choose "Last 1 Week" from the date bar on either the watch list or the data point details pages I get the following message on the screen: "Point Values Limited To 5001, please reduce the time range or adjust the rollup interval". And the chart will only display the 5001 readings.

Since I can't change my time interval because I need to compare a whole week, I have 2 questions:

1. Is the Rollup interval my data point times, such as change the reading intervals from 1 minute to 10 minute?

2. How do I change the limit of 5001 for the charts? (I cant find that setting in the system settings)

Thank you

Hi @BG,

You can change the point values limit in Administration > UI settings. But be careful with this one, your browser could crash if you have large amounts of data in the chart. Also, you can find more information about rollups in:

https://help.infiniteautomation.com/rollups/?rq=rollup

Hope this helps you,
Regards

Thank you very much guetteluis. I was looking in the wrong place for that setting. I will experiment with slow increases.
Cheers

Brian

As I just hit the same issue:

I need to set it to 35040 (365x96), but after doing so in /ui/administration/ui-settings it get's resetted to 5001 on clicking the "save" button...

Is there a limit hardcoded somewhere?

Hi mircsicz,

Is it possible your API or UI modules are out of date?

@phildunlap said in "Point Values Limited To 5001":

Is it possible your API or UI modules are out of date?

Hi Philip,
I don't think so, just ran an update yesterday morning...

BTW: I consider my issue an UI Bug, because I couldn't save the value I entered in the field (tried it with Chrome [64.0.3282.186] on a Mac [10.12.6]) but when I used the buttons to click it up 35100 I could successfully save the settings...

I was able to set the value through typing, so long as I maintain it being divisible by 100. Otherwise it sets back if you try an invalid value.

I only tried my required 35040.

So in terms of UX optimization I'ld wish to see a little message telling me that it needs to be devidable by 100 ;-)

@mircsicz said in "Point Values Limited To 5001":

I only tried my required 35040.

So in terms of UX optimization I'ld wish to see a little message telling me that it needs to be devidable by 100 ;-)

I'll remove the step attribute on the input.

That's the alternative to posting a warning that give's the user a clear reason for the failure...

@mircsicz said in "Point Values Limited To 5001":

That's the alternative to posting a warning that give's the user a clear reason for the failure...

Yes it is. I have to maintain the entire frontend codebase myself, sometimes things get overlooked.

Also as @guetteluis mentioned setting the limit that high might cause issues rendering the charts.

I'm aware of the risk. But that was the fastest way to render an energy profile of a full year...

I'm eager to learn about alternatives? Please mention any option to reduce data point without losing plot overview. like plotting a full year with only hourly value's... and showing more only when zooming in to more detail then a month...

But's better placed in it's own topic. ;-)

@mircsicz said in "Point Values Limited To 5001":

I'm aware of the risk. But that was the fastest way to render an energy profile of a full year...

I'm eager to learn about alternatives? Please mention any option to reduce data point without losing plot overview. like plotting a full year with only hourly value's... and showing more only when zooming in to more detail then a month...

But's better placed in it's own topic. ;-)

It is possible to do what you are talking about with a bit of custom code. I can provide you with an example later (bit busy right now). We can look at making this easier from the standard <ma-serial-chart> component.

@Jared-Wiltshire: THX

@mircsicz Sorry I haven't got back to you on this, I've been on leave. I am definitely looking at adding this as a built in feature so I might concentrate my efforts there.