Currently, AF search results can only be sorted by a single field. It would be useful to have the capability to specify 2 (or more) SortField values so that the order of results can be guaranteed in the result of a tie.

For example, being able to sort Event Frame Search Results by both StartTime and EndTime.

The assignment of a PI tag on which the currently logged in user has no authorization as PI point reference to an AF attribute must not (as currently) be possible.
It is possible to bypass the PI Archive authorization mechanism (point and data security) by using such attributes in AF-Analytics.

The error messages that appear when saving in the System Explorer should not be allowed to be skipped.

When you have thousands of tags in your Data Archive, you need to know wich tags are beign used and witch don't. It would be very usefull to have some diagnostic that shows wich tags are being cosumed more and from wich client.

When moving an AF element within the hierarchy in PSE using the "Shift key + Drag and Drop" approach, it can cause to create an Element reference if the release of the "Shift key" is done before dropping the element.
Having the option of right-clicking on the element and select "Move" would eliminate issues with pressing/releasing shift key and dragging/dropping the element and creating Element References by mistake.

As other vendors do, offer customers the option to purchase extended support for PI ProcessBook for security updates only past 2022 for at least one year, and reevaluate annually based on number of customers interested.

This would only apply to security-related fixes, not enhancement or other functionality updates.

Currently when viewing Time Series Data for a numeric attribute value type (e.g Double, Single) in PI System Explorer, sorting the value column will sort the results alphabetically (e.g. 1, 10, 2, 20, 3...) and not by size (e.g. 1, 2, 3, 10, 20). PI System Explorer should be able to sort Time Series Data for a numeric attribute by the size of the value in addition to or instead of the alphabetical order of the values as strings.

As a PI system user and administrator, I am interested in minimizing data loss due to a corrupted Archive. Please include an automated fix when corruption is noted. The PI server could force a shift to a new archive and re-processes the corrupted archive. At a minimum, the PI Server should force a shift to a new archive so we don't lose more data than necessary.

Adding an identity to an established large system can cause a flood of change records, leading to performance issues.

The AFDiag /AddIdentity feature will bypass this issue, but it would be more convenient to have this functionality included in PSE.

It would be nice if the PI Analysis Service could pick up a change in the Cache Refresh Interval of any AF Table being referenced by input attributes with a table lookup data reference. Currently, a service restart is required.

The article below states that AF Transformer is no longer supported:
https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=Playbook-AF-Transformer

Please copy the suggestions for AF Transformer for internal use and then delete these suggestions and the "AF Transformer" category from the feedback website.

All of the suggestions in the "AF Transformer" category can be found here:
https://feedback.osisoft.com/forums/555148-pi-server?category_id=333346

In PI System Explorer's UI, you can configure time intervals for escalation groups. If the SubscriberEscalationTimeout parameter is different from the escalation group's interval, the notification will not deliver on the right interval and there will be no indication of the setting in PSE.

Currently, the only way to modify it is to use PI Builder. This parameter should be visible in PSE as it directly impacts notification behavior.

Please provide a 'GoTo' like Funciton for Analysis Expressions to skip expressions or maybe even go back to a previous Expression.
I realize you don't have line numbers per se, but if the Expressions operate in order, could you use the Variable Name?
This would be extremely useful for skipping a block of code under certain scenarios where it's just too difficult for a mile long nested if/then.
@ Kevin G., don't decline this, vote for it ;)

A web service endpoint, for instance ServiceNow, may response with useful information to a notificate, like a ticket number. There should be a way to associate that information with the event frame that triggered the notification.

I'd like a one button click to send WW System Platform data to OSI PI. An example would be to add another check box during configuration where you could collect the data in the Historian, OSI PI, or Both.

Currently, when creating an Attribute in PI AF using "String Builder" or "None" Data References, the system does not update the timestamp associated with the attribute's value upon value change. When the end-user looks at the timestamp they see a static value: "1/1/1970 00:00:00" which is not representing the last time when the value has changed and thus very confusing. I believe that every value change should have a timestamp associated with it regardless of the Attribute type.

If you try to do Value Retrieval Method (like Min) of a Digital type tag, you will get an error saying non-numeric data. AF should be smart enough to realize that the data is actually a set of integers and not try to read the string representation.