• State Not Answered
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 144 views
  • Users 0 members are here
Options
Related

How to receive the delete event when Recalculate using Analyses?

vike

When I use PI Analyses for the recalculate task, I choose the "Permanently delete existing data and recalculate" option. Therefore, the old results will be deleted before generating new results. My question is how to listen to the deletion event of the old results through AF SDK. I registered these attributes and only received the refresh event.

How should I listen to the timestamp of which events have been deleted? I am using AFDataPipe signups.

Thank you for any suggestions.

Parents
  • 0

    AFDataPipe Class

    An AFDataPipe is a collection of AFAttribute objects that are signed up for data change events on the server.

     

    One well-known "secret" about the AFDataPipe (and PIDataPipe too) is that it really does not implement a PUSH model for changed events. Rather, you will have to issue a PULL. Some oftentimes just put in a timer in their code that periodically issues the pull.

     

    Since you are already using this, I presume you have no issues with AddSignUps. Your data pipe will then pull the changed events via a GetUpdateEvents call or a GetObserverEvents call.

     

    IF any changed events are found, they will be coming to you as an AFDataPipeEvent. This object has an Action property which is an AFDataPipeAction enumeration. Delete is one such Action.

     

    Based on the given AFDataPipeEvent, its Action, and its other properties like Value, you should be able to know everything you need to know about what was changed. Note the Value is an AFValue, and that AFValue has an Attribute property to tell you the AFAttribute that was changed.

     

     

     

Reply
  • 0

    AFDataPipe Class

    An AFDataPipe is a collection of AFAttribute objects that are signed up for data change events on the server.

     

    One well-known "secret" about the AFDataPipe (and PIDataPipe too) is that it really does not implement a PUSH model for changed events. Rather, you will have to issue a PULL. Some oftentimes just put in a timer in their code that periodically issues the pull.

     

    Since you are already using this, I presume you have no issues with AddSignUps. Your data pipe will then pull the changed events via a GetUpdateEvents call or a GetObserverEvents call.

     

    IF any changed events are found, they will be coming to you as an AFDataPipeEvent. This object has an Action property which is an AFDataPipeAction enumeration. Delete is one such Action.

     

    Based on the given AFDataPipeEvent, its Action, and its other properties like Value, you should be able to know everything you need to know about what was changed. Note the Value is an AFValue, and that AFValue has an Attribute property to tell you the AFAttribute that was changed.

     

     

     

Children