When a backfill or "recapture events" option is selected for Event Frames, give the user an option to "Save Annotations" for that specific event frame. Right now, we use Event Frames to copy in Reason Codes and Comments (that are logged as annotations) so we are limited in backfill or recapturing the data if historical data changes.

‘Outputs at close’ is very powerful and flexible. It allows one to use expression analysis syntax in event frames. Unfortunately, it is only available for generation mode 'explicit trigger', but not for 'pulse', 'step', or 'step continuous'.

If you want e.g. a new event frame started every time a value of an input tag changes (and closed again when it changes again), generation mode step continuous is what you need.
In that case it would be very helpful to also be able to use outputs at close.

When manually creating an AF Table (i.e., an internal AF table) in PI System Explorer having the ability to specify a NULL value would be beneficial. Not all datasets require a value for each cell and not all tables need to be linked to, or imported from, external systems.

The ability to utilize three columns as input for interpolation from an AF Lookup Table to determine the result for a fourth column could be beneficial for predictions and analysis.

Currently, only linear and bilinear interpolation is possible from an AF Table Lookup.

There are no number base conversion functions available in AF Analysis. There are many situations where I need to convert numbers between different 'number bases'. I frequently work with MODBUS devices and there are many times number base conversions are needed to properly get data.

Example: Convert decimal to hex, hex to binary, etc.

I test many of my functions using Excel before implementing them in Analysis. Excel has functions such as HEX2BIN, DEC2HEX, etc. I'm actually surprised that, after many years of AF/Analysis development, these type functions are not available. These are valuable functions that should be implemented.

We would like to be able to extract the data reference type (PI Point, None, Formula, Table Lookup, etc.) for an attribute using PI Analysis, similar to the TagType function for PI points.

When input PI Tags are referenced in PI Vision 2020+ calculations, they do not automatically detect PI Tag name changes. For users with a lot of calculations, this can be extremely problematic in the event of a PI Tag name change. In the event of a name change, the following error is produced: [-12301] Performance Equation parsing error. Possibly updating the PE scheduler to reference the PointID instead would be beneficial.

Looking for a way to have multiple reason types for AF attributes.

As a user, I want to have the option of entering a service account's Windows credentials when authenticating to a Table Connection in PI System Explorer. Currently, the Windows authentication mode only allows impersonation of the user running PI System Explorer.

large value display as 1.23 E+008 format instead of the orginal value in PSE Pop-up Trends

if the trend can follow display digits, it will not show scientific nonations

Currently, while the UI can recognize parameter types as multi-dimensional arrays, the configuration UI for a Notification Rule does not allow access beyond the first array dimension.

It would be useful to have full support for parameters configured as multi-dimensional arrays (i.e "MyType[][]") in addition to the exsisting support for 1-dimensional arrays ("MyType[]")

Can PI AF be connected to physical properties databases (libraries) such as AIChE Dippr or Aveva Thermo or others in order to programmatically call for physical properties data in realtime. (Centralize calcs in AF)

When troubleshooting intermittent issues, using AFGetTrace may be problematic as the trace can consume quite a bit of disk space, and setting a maximum file size will cause the trace to stop once the file is full. Without knowledge of when the issue will reoccur, we are stuck either risking filling up the disk and having a huge trace file to analyze, or set a max file size and possibly miss the issue.

Automatically display UOMs in the PI AF client in the language of your choice i.e. not a conversion of units. For example, to change the display of UOMs to Russian instead of English, kg becomes кг, V becomes B.

Creating a Polybase External Table with a PI SQL Client connection via ODBC causes query errors showing only it only supports column-wise binding. Polybase attempts to utilize row-wise binding which is not supported. Developers and customers have shown that Polybase is unable to be instructed to utilize column-wise binding instead.

When querying against an External Polybase Table the following errors are shown:
Function "SQLSetStmtAttr(0x2485bf85640, 5, 0x1d1f, 0)" was called.

Function "SQLSetStmtAttr" exited with an error code -1.

Error: [PI SQL Client] Only 'SQLBINDBY_COLUMN' is supported.

In an AF Hierarchy where an element contains dozens of Attributes - each with Child Attributes - I am interested in only bringing back all top-level attributes. The use case is that the top-level attributes may not have any naming convention in common but are all defined as PI tags (Child attributes may or not be PI tags). I would like to just bring back the top-level attributes in PI Builder so I can quickly modify tags en masse.