Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
"Point Values Limited To 5001"
-
Thank you very much guetteluis. I was looking in the wrong place for that setting. I will experiment with slow increases.
CheersBrian
-
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.
