1 of 1 people found this helpful
Fundamentally those attributes have values that depend on the query time, so an event pipe is not all that meaningful in terms of telling you that a value changed. AFAIK, there is no update to AF 2.7 that would fix this.
Just polling the attribute when you need it is one option. But again the window is moving based on the current time, so the value can change even if there is no new data.
A more sophisticated strategy is to get the underlying PI point and monitor that via the event pipe. When that receives a value you go and retrieve the value from the attribute. So getting a value over the event pipe doesn't indicate a new value for the attribute. It is just a signal that the attribute should be queried again.
Hi Mike !
Your idea is very interesting !
However, there are another kinds of attributes not supported by eventpipe that depend on more complicated scenarios, like rollups...
So, I think that use two strategies (eventpipe and pooling when eventpipe doesn't work) will be more easy to support and mantain...
Thanks for your help !