PI Vision should be able to directly pull entire  table objects (such as linked tables) from Asset Framework into a display, rather than forming a table of attributes with Table Lookup data reference.

As a PI Vision user, I want to use an AF hierarchy Tree View to switch the asset context of my display so that I can navigate to the asset I'm looking for.

It is great that I can attach files as an attribute to an element in AF and that these files are shown in the PI-Vision navigation (see attached screenshot). But why is it not possible to open these files directly from PI-Vision? This would be a great improvment.

As a PI Vision user I want to be able to switch the units of measure on my displays between Metric and Imperial so I can see data in units I expect. Adding support for AF UOM groups would allow the user to make this choice.

Allow dynamic search criteria to be added to a trend so that it can dynamically display data from assets based on the specified search criteria (attribute values, attribute name, attribute category, etc).

Assets and machines are never quite the same. Be able to swap the asset/element context (may be different template) and if the selected asset doesn't have certain data available on the display or if it is marked as excluded, don't show it on the display rather than an error message.

This should apply to collections in addition to individual symbols.

Handle the ability to trend data from attributes across AF Element Versions. 

For example, when old sensors have been replaced with a new control system, new tags are created and customers use AF Element Versions to manage the mapping between the old and new tags.  Users would like to use and visualize data across this versioning time point.

As a user of PI Vision I would like to be able to swap through assets based on their element description rather than element name as it is easier for me to identify the assets as such.

We noticed that if we created in PI AF a parent template with a nested a child template, and subsequently instantiated the nested parent/child template in a PI AF hierarchy, PI Coresight would only recognize the instantiated parent asset in a related asset search. For example, in PI AF we are creating a parent template for a reactor and are looking to nest a child template for a weigh scale that only applies to a subset of all reactors. We want PI Coresight to return in a related asset search all reactors and the weigh scale where applicable.

As a user of PI Coresight I want to be able to swap context at a parent (plant) level and propagate new context to child elements relative to the AF model hierarchy.
Currently only information on the Coresight display part of the same element template are concerned by the swapping.

Many times PI Administrators develop screens but are not the process specialists. The process user might see a "red" condition that is false and wants to quickly change the attribute limit (hi or lo) value so that it is no longer "Red". Rather than communicating to the PI Admin they should have the access to change it themselves without having PSE installed on their system. Saves a lot of time and work.

As a custom data reference developer, I would like my bulk AF SDK call implementation to be supported in PI Vision as this should improve the custom data reference performance when multiple custom data reference attributes are in the same display.

Add capability to add element's description to symbols, without the need to create another attribute for that, so element relative titles and labels are easily shown on a display.

Currently PI Vision suffers from serious performance problems when displaying more than a handful of table lookups on a single page. What is the point in having table lookups in AF if we can't effectively visualize them in PI Vision?

It would be useful to be able to get the analysis status for an element into either an AF tag or a PI Tag.
Reason for this is I have a set of traffic lights that monitor certain statuses of tags, and if the analysis is off/failed then I can handle that as a traffic light status (with a formula) instead of showing a potentially incorrect status because the analysis has stopped.
I suspect that I can fudge this by linking the sql analysis table to AF and using table lookup to get the status.

Show the AF databases used by Pi Vision displays so users can verify that Displays will not break in case they need to delete or rename AF databases