Cumulocity IoT Feedback Portal
I have a use case with logical devices that send batches of measurements.
It happens that the data is completed or recomputed at ground side and measurements are sent again to Cumulocity.
We experience problems when deleting existing measurements before inserting new data. And Cumulocity does not allow to separate multiple measurements recorded with the same timestamp.
A solution suggested by R&D (cf. https://getsupport.softwareag.com/servicedesk/customer/portal/2/SI-501596) that could help would be to natively add a field "received_time"
The value of "received_time" is the current timestamp at arrival in Cumulocity.
It comes in addition with the field "time" that represents the measurement gathering timestamp.
With that new field, the process fed from Cumulocity measurement api would be able to distinguish the corrected measurement from the initial one.
Hi Philippe,
To date Greenflex is the only customer who has requested this capability and although we have had some internal discussion about this we are not in a position to prioritize this on our backlog, The question is not just about providing another field as standard, but also how to allow querying against that field, any additional indices that would be needed etc. Should the situation change in any way we will be in touch.
Regards, Jane.
Hi Jane, hi all,
was this suggestion examinated by the R&D ? Is there any chance to see this feature implemented in one of the next releases ? It would be nice
Best regards
Philippe
We will consider this for a future release. In the meantime it would be useful to understand a bit more detail on how this would be used. I will set up a short call.
Regards, Jane.
Yes, a field 'received_date' natively filled by the C8Y backend on the measurements would be great for some cases where devices repost data (corrective measurements, ...).
This way we can identify the up-to-date information.