Common DpArchive setting

[schu]

Hello,

I have datapoint type as seen in the attachment and the archive config is added to the root node of the datapoint. (That's just a similar type I'm using for the project)

I use a single dpSet function to set all of the datapoint elements at once (never otherwise) and "atomicDpSet" is not set in the config file.

When I do a dpQuery with a timerange filter, what I expect was to get all historic values with all datapoint elements' values. However, the problem is visible on the screenshot of the table widget. There is a ladder-like record history, which feels like dpSet is setting the datapoint elements group by group and creating individual archive entries for all of them in the database.

We did not face it until recently, and was curious if we need to enable atomicDpSet and if it is really going to fix the problem?

We are not able to reproduce the behavior as we like, so if we can get an answer it would be amazing

Thanks in advance.

[leoknipp]

We do not know how to read the entries in the table. The time column looks weird as there are correct times and times starting with 1970.
When doing the historical request of data you can use "-rcv 2" at the manager who reads data to see what the result is.
Maybe only the function to fill the table is wrong and therefore you get the "wrong" result.

Best Regards
Leopold Knipp
Senior Support Specialist