As a user, I want to be able to search for specific PI Points used by PI AF attributes, so that I can easily find where the PI Points are being used.

I would like to use some more advanced string functions such as Split, Len (string length), and even regex filtering to allow more fine grained control of how some input strings (such as attribute values or substitution parameters) are manipulated to create a new string output.

If you have a PI Point attribute with auto tag creation and you want the attribute UOM and PI Point engunits to match, you have to define it twice; once in the attribute UOM field and a second in the attribute configuration string, e.g. engunits=m3. If there was a substitution parameter for the attribute's UOM, you could use it in the attribute configuration string, e.g. engunits=%AttributeUOM%.

PI System Explorer should visually highlight attributes of template based elements that have changes to the template.

As a user, I want to be able to use substitution parameters in attribute template descriptions, so that when elements are created from template, the attribute template description can be substituted with pertinent information.

Note: This was previously Enhancement 116200.

As an user I want to be able to create a template hierarchy (parent-child) all at once, so that I can easily create a hierarchy representing related assets. For example, create a motor, gearbox, compressor train with a single template that actually consists of (in this case) 3 templates.

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.

As an end user, I would like to be able to change the timezone referenced in PI System Exporer from client timezone to server timezone. Something similar to the "PI Data Archive Time Zone"  setting found in PI DataLink would be helpful.

A feature to review the changes that will be made when importing AF templates that have been exported from a lower environment.

Example.
Make changes to element/attribute/archive templates in dev.  Export library to XML.  Compare export to QA templates and provide a report on what all will change to be reviewed before importing.  If it has only the changes you intend to promote, then you can go ahead and import.

Would like ability to use substitution parameters in attribute template names.  Using PI-SNMP for Linux file partition data. We need to know the storage index# in AF since they vary server to server.  Want to provide users doing searches the actual partition name and the data for them, instead of using Storage Index name attribute (tag value) to determine which is which.

see https://pisquare.osisoft.com/message/77201-substitution-parameter-in-attribute-name-of-template?q=substitution parameters in attribute

It would be helpful if you could search by Element Category or Element Description when searching for Analyses in PSE. My setup is 5 templates (CHW, Water, HW, Electric, Steam), each of which have accounts that can come from 5 different sources (selectable by element category). I can't filter by both commodity type AND source, I can only do Commodity type using the "Template" criteria option, as the "Category" and "Description" search criteria options relate to Analyses, not to elements. This severely limits the functionality of the search feature for me.

Currently, when you remove a template from an Element in PI System Explorer, you'll remove all existing attributes from the Element.

There should be a functionality in PI System Explorer to remove the template without making changes to the attributes for the element.

Currently, the only workaround is to use PI Builder to remove the template without removing the Attributes associated with said Element.

Allow for PI AF templates to be version controlled. Include the ability to revert to previous template version, or continue to use old versions for specific elements. This will reduce the risk of deployment and improve change/release management process.

Currently analysis runtime information can be accessed programmatically using the AFSDK (AFAnalysisService.RuntimeInformationFields - https://techsupport.osisoft.com/Documentation/PI-AF-SDK/html/P_OSIsoft_AF_Analysis_AFAnalysisService_RuntimeInformationFields.htm). However, there are no fields which can be specified corresponding to backfilling/recalculation status of an analysis.

Adding a field for the aforementioned property or introducing a new method which could expose backfilling/recalculation status would be helpful for finding backfilling/recalculation errors programmatically. This approach should be much faster than finding analyses with backfilling errors in PSE.

Would like AF audit trail to retain friendly database name for deleted items.  Currently it removes the friendly database name making it very difficult to track changes made to a specific database once an item is deleted.

As a PI System Explorer user I want to be able to see when was the creation date and last changed date of an AF object without enabling the Audit Trail, similar to the PI SMT feature which is easily accessible and works by default.

Please allow one to export, and import, to XML from PI System Explorer Contact Groups and/or Contact Delivery Endpoints.  Doing this with AFExport.exe and AFImport.exe on the AF Server is cumbersome and restrictive.