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

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.

As PI Vision user I would like to embed critical process equipment's video to our PI Vision Displays so that I can see how the equipment is functioning in real-time.

Hello,

is it possible to assign the symbol to one attribute of the AF element/ tag but to present the label (name) from another attribute (string) of that same element?

Currently we can set the Y-Axis limits to be dependent on the plotted values or set both the upper and lower limit.

I would like to be able to fix either the upper or lower limit, and have the other limit still be dependent on the plotted values.

Ability to see annotations, such as those from Manual Logger, in Pi Vision.

In PI Vision, the hyperlink can be enable/disable based on different AF attribute values

When we want to show the timestamps and values at 2 very close points of time, the trend cursors (sliders) will overlap each other by default, obscuring the timestamps.

Of course, we can zoom in the trend so that the sliders are further apart.
But there will still be times when a broad range of duration is needed to be shown at the same screen with multiple slides and information needed at different points of time. Hence, it'll be good to have such a feature to allow users to freely adjust the height of the slider boxes.

Add ability to control what is shown in the Name column. This should have the same options as other symbols: attribute name only, description, asset name, or use custom label to provide a friendly name

Configure gauges using multiple attribute values. As an example, if you have a tank that has 2 level sensors, it would be helpful to show both levels in 1 gauge. Currently we accomplish this by creating 2 gauges and putting 1 on top of the other, but having a single symbol with both would be more functional.

Ability to control the font size of a text symbol based on a data item's value using the multistate functionality of PI Vision.

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.

you should add log scales for all symbols..

To be able to have event tables within Collection (this is mandatory)
Event tables are feed with events matching the collection asset.

It is different than the idea https://feedback.osisoft.com/forums/320517/suggestions/35062504

drop down menu without having to create a collection. Collections error out if attribute is not available for a certain element.

To be able to:
- change the color of the Acknowledge button
- hide the event name column
- change the order of the columns
- add any event frame attributes as columns

Would be great to superimpose Event Frames within a trend: in the same symbol. Really interesting when analysing a process or when troubleshooting.

Would be great to be able to:
- have cursor(s) on XY plots