Filter expression for inputs to a Rollup

I'd like to be able to utilize such functionality for weeding out bad data. If the value is questionable or if my 'Data Quality' attribute is 'Bad', I don't want that value to be included in the rollup. That would prevent stale/bad data from distorting rollups.

First mention of this improvement was more than 8 years ago. Is there any new on this?

In general, why does it takes years before we go from a 'no status' to any other status?

This gives us, clients, not really the impression that our ideas are being looked at/taken seriously.

Upvoting this request

We need a mean to be able to filter an expression on a condition like: "what is the average load on a motor for the last hour only when it is running".

agreed . . . one of PIAF's biggest short comings in comparison to Excel Datalink is not having an easy, intuitive way to do any of the calculation functions with a filter. I understand it can be done with multiple analyses, but that approach gets messy with all the extra outputs and analyses that are simply intermediate values.

This would be very helpful trying to totalize/manage various liquor inventories in a kraft pulp mill liquor cycle.

Encountered a similar case :: user was was trying to rollup the Volume (Attribute, PITag) of separate Tanks (Elements) that had variable content types (Attribute, PITag). Since the tank content is changing, the fairly simple conditional sum of Tank Volume required ACE code.

I find this useful as well, but would like to request if string concatenation could also be included?

As touched upon by volljm below, I would extend this to ensure that System Explorer analysis configuration has most of the functionality that PI Datalink has. This makes it easier for power users to migrate to a PI admin role.

Tank inventory volumes by product type. We cannot use a fixed tank product type, because the products can change. So the ability to add volumes based on the current product requires this flexibility.

This feature would allow counting active alarm tags. Currently it is only possible to rollup active alarm tags if the active state has the state no 1. In my current case, there are a mix of tags from different control systems and for some state no 1 means inactive. There are workarounds, but a filter expression would be easier to implement and keep configuration simple.

This would be super helpful in my case here: https://pisquare.osisoft.com/thread/43796-can-an-analysis-reference-the-status-of-child-elements-attributes?sr=stream

I would like to have this function for compare engines only on running.