Right now I get errors in Event Viewer on my Vision server saying "Server is not available".  The server it mentions is our Dev server, which means somehow a tag or attribute got to Prod without being converted.  But the error doesn't tell me the tag or the display.  So I have no way of troubleshooting this without individually checking each and every display or spending all my time digging through the SQL to figure out where all the config information is hidden.

The other use case is: if as a PI admin I want to change the name of a PI tag or AF attribute, I would like to do a quick search of our displays to see who it would affect.  That is not possible right now.

I realize this is complicated by collections, but if I could even get displays as they are configured in their saved state, that would be far beyond what I have now.

Currently in a PI Vision Trend you can only see the full Attribute Path by hovering over the attribute name in the legend. If the attributes have differently named parent elements, then the legend will show the Parent Element and attribute name only, it will not show the parent element's parent element or more than that. If the parent elements are named the same, then the PI Vision trend will only show the Attribute name. For example, in the attached image there is a trend with 2 attributes named "Attribute", the first one has the following path: "\AARVM1\854090\Parent1\Child 1.1\Child 1.1.1|Attribute", and the second attribute has the following path: "\AARVM1\854090\Parent2\Child 1.1\Child 1.1.1|Attribute". Both attributes have identical names, and identical parent elements, as well as identical parent element's parent element, however the 3rd parent elements, going up the AF hierarchy, are different, but PI Vision only shows the attribute names. The only way to distinguish between either one of these attributes in the PI Vision Trend is to hover over the name of the attribute in the legend, which shows the full path. It's also not possible to distinguish between these attributes in the Trace Options without hovering over the attribute names. My suggestion, which is linked to case 854090, is to give the user an option to view the full path in the trend legend or to be able to choose how much of the full path to display in the trend legend.

I would like the PI Vision Display Utility to give me a warning and options if I try to move displays to a target database that has existing displays with the same names. This would avoid unintentionally creating duplicate displays with the same name.

It might also be useful if the tool gave me options in this case such as:
1) Acknowledge the warning and create the duplicate displays
2) Rename the new displays before adding them to the target database so  that they are no longer duplicate names
3) Overwrite the existing target database's displays with the new displays and keep the original target display's DisplayID.

For graphed data in PI Vision, I would like to be able to use limits on the data (either direct to the point definition or local to the PI Vision page) to either have the data plot line change color on the display as it passes from normal to hi to hi-hi to OOT. (or the background to change so if you cross HI, the background is now yellow at this point moving up).

This would be similar to Multi-State options which do not, today, exist for graphs.

I use dozens of plots in a column with from 1 to 4+ points per plot but am focused on a graph where I could have 1 primary point that controls the background/line color (or multiple lines changing color would be amazing). This would allow me to more rapidly see lines passing through phases/oscillations that are outside of our desired bands.

The PI Vision Display Utility should be able to find and replace PI Points and AF Attributes by name.

A situation where this could be necessary is as follows:
1. A PI Vision display was built for using PI Points from a certain data source
2. A new data source, possibly a new instrument, is added to read the same process data. The old data source is taken offline.
3. To keep data separate between different instruments, new PI Points are created for the new data source. New AF Attributes referencing the new PI Points would also be created for similar reasons.

Currently to update the PI Vision displays with the new PI Points one has to go through each display and replace all instances of the old point with the new point.

It would be great if Vision display start time and end time could be configured together. Whenever I change start/end time of a trend, PI Vision immediately requests for data from PIDA even though I haven't finished entering the start/end times.

For example I have a trend with last 8 hours of data. Then I want to check data back in January 2010. When I enter 1-Jan-2010 into the start time field and click on end time field to set the end time of the trend to 1-feb-2010, PIVision already fires a query to PI Data Archive before I have the chance to change end time of the time range. This means that PI Vision asks for data between 1-Jan-2010 and now. This can be a very expensive query which can run for a very long time. If this repeats multiple times, PIDA can get overloaded.