Allow the UFL interface to delete PI tag data or provide some other supported automated method of deleting PI data from a collective.
There is no way to easily delete data in a time range if you want the changes to occur on both the primary and secondary data archive. It seems the UFL interface would be good to use to do this. You could provide it a tag name and time range and then buffer the delete to both collectives, so the data does not exist on either.
Heather Boehler
shared this idea
3 comments
-
Tyler Wipf
commented
This would be nice to add on as an option to have handled by something in a programmatic fashion, especially if the buffer subsystem would allow for it.
-
sjohnson
commented
There is definitely an opportunity to streamline deleting data in a collective environment. Currently, we have to jump through programming hoops to ensure data gets deleted from each server in the collective. It would be much preferred to have buffering or other technology handle deletes automatically, as it does for data sending.
-
ehoffman
commented
Since the collective prefers data to be sent through buffer subsystem in order for it to be written to all collective members what if buffer subsystem could also handle delete requests as well? I feel having buffer subsystem handle this would really help keep servers in sync when writing and deleting data to tags.
We have a lot of manual entry process where we are always writing and deleting and or correcting data. It would be nice to have a OSI supported producted that could handle this vs creating custom VBA code or other methods to handle deleting data on collectives.