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.
Data Source can't read variables if more than 100 data points
-
Hi, All,
Hopefully this is something others have come across and there is an easy fix.
We have a scripting data source which has more than 100 data points. In our script, we try to set the value of all the 100+ data points. The problem is that the script says that all of the data points past the 100 mark are undefined.
IE: if we say varDataPoint101.set(true) or varDataPoint101.value then the script validator says varDataPoint101 is undefined.
Is there a way for the script to pull in and recognize more than 100 data points that are associated with it? We're also using the CONTEXT_POINTS object which seems capped at 100 as well. I'm guessing a fix for one will be a fix for both.
Thanks,
Chad -
@cmusselm I'm not aware of any 100 point limit, but we will look into this. As a temporary work around you could use the QueryBuilder utility and place tags onto your points, then query for them in the script.
One more thing, are you sure all of your points are enabled? This would explain it If only the first 100 are.
-
Sorry I said QueryBuilder but I meant the DataPointQuery utility, you can read about it here:
-
Thanks, Terry, we will try that.
Yes, they are all enabled. If we just save one that is considered undefined, then it will "fix" that one, but it pushes another one out of the list. Almost like it just recognized the 100 "newest" or most recently saved.
Thanks,
Chad -
This post is deleted! -
Wanted to check in and see if this issue was able to be re-created, and if there are any updates.
Thanks,
Chad -
Hey Chad, I wonder if you could break your set command up into 2 or more operations and if that would work? That might be helpful. I'm not aware of any other use cases where we have done this but I don't see why it wouldn't work.
-
I know it's been a while, but I wanted to let others know what I found with this.
I created a test scripting data source with 110 data points. (I would post it here, but its 5700 lines and I don't have permissions to attach the file.) I basically use the .set for all 110 data points.
When I clicked the validate button I would get the following error:
ReferenceError: "varDP110" is not defined at line: 28The error was not generated when the script ran on its normal schedule, so from what I can tell it's something related to how the validate button pulls in the variables for the script to run.
Thanks,
Chad
