cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Best practise to store historical data plus live streaming data in a Thing

SOLVED

Re: Best practise to store historical data plus live streaming data in a Thing

I used QueryNumberPropertyHistory and just came to know the data is storing in chunks. I uploaded CSV file with 238 records and only data got saved in ValueStream is 30 records and strangely random data not in ascending or descending order.

I probably be using wrong format of date in CSV

2016-01-31,608,0.0976,20,7.1

2016-02-29,558.0457329,0.1052,18,7.2

2016-03-31,449.9114189,0.08536,22,7.2

2016-04-30,464.1673867,0.0876,25,7.1

I have uploaded so many data in many entities and now realized they all got uploaded wrongly.

Highlighted

Re: Best practise to store historical data plus live streaming data in a Thing

Hi,

For what I see on your csv file, you have only Date  and you don't have Time, then if you import that data all the Data at the same day will be overwritten ( I don't know if this is the problem ).

Query one property by one with "Query"+baseType+"PropertyHistory" to see which data it's recorded on each Property

Re: Best practise to store historical data plus live streaming data in a Thing

Hi Carles,

I have resolved the issue. It's not about passing the date-time value in CSV, I had to change the date format in params object:

dateformat: "yyyy-MM-dd HH:mm:ss"

The string should be in exact above format (Case sensitive) to make it work.

Thanks for your support.

Regards,

Neetu