For this particular use case, you should be able to use the TagTot() function which executes at 6:00am with an output timestamp override for 5:30am. It’s not clear why you’re using output as input. Can you provide an example?
Reopening this suggestion to collect additional feedback.
An error occurred while saving the commentJoshua Duncan commented
I'd like to add to this suggested improvement. I'm using PI System Connector and ran into a scenario where the archive modes are necessary. I have an OPC Alarm and Events interface pushing to a "source" PI Data Archive and System Connector/Relay sends to a "destination" PI Data Archive. There are events that occur at the exact same timestamp that are substituted by default at the destination. Having the archive modes (similar to the PI to PI interface) would be ideal:
ARCNOREPLACE add unless event(s) exist at same time (PI 2.x)
ARCAPPEND add event regardless of existing events.
ARCREPLACE add event, replace if event at same time.
ARCREPLACEX replace existing event (fail if no event at time)
ARCDELETE remove existing event.
ARCAPPENDX add event regardless of existing events, with no compression.