For example, a display containing two value symbols that display data for a tag. One value symbol shows the value for the tag at a specified time yesterday and the other one shows the value if the tag at a specified time today.

Is there a possibility to add error bands (or error bars) to a line plot in PI Vision? The error band could be based on an error signal, or two absolute value signals for the min and max. The error band most often show a confidence interval for a signal, and can vary across time, so visualizing a standard deviation only is not necessarily sufficient.

i would like to give more details to amchart 4.0 and pi vision.

We have link using rootpath and we want to be able to change Search root not only in collections, but in Assets switching Roll Down menu too.

Trend y-axis scales should be able to be shown on both sides of a trend.When plotting two tags with different scales, having one scale on the right and one on the left would improve trend readability.

It would be nice to display attribute traits such as maximum and minimum on PI Vision; it can only display targets

Currently, the font size is directly related to symbol size. This is problematic when migrating button symbols from PI ProcessBook to PI Vision, since they will not retain their width. This leads to manual work being required to adjust the display layout after displays are migrated.

An alternative solution would be to add a button symbol to PI Vision that can be sized independently of the symbol's font size.

Not all users like synchronized trend cursors (placing a cursor on one trend causes it to appear on other trends at the same time), some find it very distracting. There should be an option to disable this functionality.

Want the ability to set multistate behavior on a attribute column based on another asset value – similar to Value, gauge and drawing symbols. If this can be done – should be able to do it as well for attribute columns which are strings. I would think it is based on a cell in a table at that point.

Fill the area between the trend line and 0 (or a configurable value) with color. This makes deviations from a desired value much easier to see.

Using URL parameters I am aware of being able to select either single or multiple scales for ad-hoc trends.
I would like to be able to specify the zero and span of the ad-hoc trend via URL parameters. This would standardize all ad-hoc trends shared between our PI Vision Users without needing to update the database settings for our data items or manually adjust each ad-hoc trend.

Hi
When you have many users, it would bee nice to have an \ext\ area where you did not make trouble for other users.
This possibility could open this good Custome Symbols for more people :)
Regards
Ulf

Symbols have their own initialization function (init()) that allows me to run script when a symbol is loaded on a display.

I am wondering if I can accessa similar onLoad() or Init() an a PI Vision display.

I am wanting to access features within PI Vision such as:
-Creating a new display
-Saving a display
-Moving a display from one folder to another
-Querying information about each display (such as number of symbols, symbol types, display owner, etc..)

Is there some kind of API that can be accessed to do all of these things?

Or maybe it's possible to change the which symbol that comes first when dragging a tag out in a display?

Displays with collections may have standardized filtering applied and it would be useful to allow other users to modify the criteria.

Add symbol collection search criteria to filter assets by the existence of related event frames active over the time range of the display (HasEvents?)

Allow the acknowledgement state of those events to serve as an additional filter (HasUnacknowledgedEvents?)

Integration would then be seamless between symbol collections and event tables, where events may be acknowledged from within PI Vision directly.

Provide a multistate toggle to synchronize a symbol's data reference with the multistate reference. When changes are made to the symbol's data item (e.g. display reuse) the multistate will reflect that change too.