Problem resolved. So I discovered not all our data sources have identical point names and one of the common points I was using to identify its device name did not exist in certain DS so it reverted to the previous values in the data sources array.
This was nothing to so with the JSON store functionality and its all working as it should now . :) Thanks again guys.

It works with double quotes and needed double quotes around the value rollup-type = " 'DELTA' "
... I love the design of this engine, It's a powerful tool for sure.
great job team!!

At the end of the automated emails we send out, can we change the signature line to something beside Mango Automation?

Sorry guys I was not thinking about this correctly of course the watchlist parameter is saved with the default value to the parameter. I was confused. :(

Thanks for the help I am navigating through the new UI and getting most of it to work as I need. I was able to get the DS import working.

One last question about the JSON importing. I create the Excel reports normally by exporting the report template in csv then manipulating the references in Excel and then back in again using the csv import. How should I now get this excel Report template exported to a csv format and re-imported back into the system as an excel report template?

When I am importing what do I put in all these extra fields like pointfolderid and id ???
Plus a lot of fields exported with the word OBJECT in them what does this mean on import?

OMG thank you... That's a relief, thank goodness.

Guys I really appreciate your work on the look and feel of the new UI. It seems to work well and I do like the new Datasources screen however there is one area that I need your advice on how to overcome, the removal of the csv DS import export has perplexed me as I see no viable solution to building large interrelated meta datapoint models using JSON only. We build out meta points in an excel spreadsheet so we dynamically inter relate the xid's in the script point event triggers and then import this through csv to create the 2000 point meta data sources . Which tools can convert the csv to proper json to make it appropriate for import?
.

Thanks no that was not in the script I added that after. This produces the same result. It is 3.6 and I will upgrade to 3.7 shortly if it fixes this. Thanks for your reply,

var dataPoints = JSON.parse(JsonEmport.dataPointQuery("eq(name,FAN COIL VALVE)&limit(1000)")).dataPoints;
print(JsonEmport.dataPointQuery("eq(name,FAN COIL VALVE)&limit(1000)"));

I used this code before our last update to 3.6... now this returns an eof error.

print(JsonEmport.dataPointQuery("eq(name,FAN COIL VALVE)&limit(1000)"));```

Expected } but found eof //JsonEmport.doImport(JSON.stringify({"dataPoints": dataPoints})); ^ at line: 8, column: 90 at line: 8, column: 9

I am trying to bulk edit the rendering properties of a point and it is saying an error is the XID is already in use?? So am I doing something incorrect here?

No BULK edit feature working is a pain since I the export for csv was removed .

I would like to hard code the date.to and date.from on my dashboard. Not sure how to initially set with ng-init the date.from to Date("2019-01-01") and date.to Date("2019-12-01") ?

Further to that I recursed one more level to successfully fetch the previous value. So what is going on that I have to do it twice to see the increment. I understood this function would return the value directly before the time passed in?

var KWBF1 = KW.pointValueBefore(KW.time);
var KWBF2= KW.pointValueBefore(KWBF1.time);
print(KWBF1.value);
print(KWBF2.value);
print(KW.pointValueBefore(KW.time).value);
print(KW.value);

Success. result=Success, no new value, timestamp=13:09:36
6622.0
6621.0
6622.0
6622

Wondering why this code is producing the same values with data that has unique values. I use.pointValueBefore to get the previous value for comparison and the function seems to have stopped working.

print( KW.pointValueBefore(KW.time).value);
print(KW.value);

Success. result=Success, no new value, timestamp=12:53:54
6620.0
6620

both produce the same result value so what is going on here?