When making use of the GetValue transposed function when creating a new Template specific Data Model, we can see that under the hood it makes us of the AF SDK call AFData.InterpolatedValue method to capture the data at a specified timestamp provided in the transposed function. This method does make use of any Retrieval Modes.

It would be good for this GetValue transposed function to make use under the hood of the AF SDK call AFData.RecordedValue method instead since this method offers the possibility of using Retrieval Modes like "AtOrBefore" which is really useful to capture the last archived value before the timestamp provided.

This would provide a more faithful aspect of the behavior of the process.

Be able to use RTQP to access PI Points and Config strings (DA Directly)
Use case:
create a dashboard that lets me know the amount of bad data (tags) mapped to our AF.

(eg. “Bad Input”, “Calc Failed”, etc)

Our system has numerous tags and it is impossible to monitor them one by one.

The RTQP engine has allowed us to query massive amount of AF Attributes to get their current values easily.

Some AF attributes have been excluded in our system. For that case, we are not interested whether or not the values are bad.

Hence I would like to know if I can filter out any AF Attributes that are ‘excluded’ in my query.

The resulting query will give me current values of the attributes that are bad.

Without knowing the tag names, it is impossible to rectify those bad inputs. We would need to open up AF again and trace the AF path to find out the tag names.

It also limits our ability to deep dive on root cause using the same query. (eg. Multiple tags from the same interface are showing bad inputs – this is impossible without knowing the tag names).

It would be useful to be able to access a specific row from a PI SQL Client call. For example if I query muiltiple attributes indicating some KPI ordered from highest to lowest returning 1000 rows, I might want to show only the top 10. The TOP function is supported in SQL Client, but the Table Lookup DR in AF only allows you to find the first row.

It would be useful if either the row number, 1..n, was returned or the table lookup DR would allow you to pick a specific row. This would then allow you to show the top n results in a table in applications such as PI Vision.