It would be nice if you were able to keep a Pi Vision board and change the pi value that is associated with a given visual. For example, I'd like to keep a stack of Horizontal Gauges and just change which pi value they are showing. Instead I have to navigate to the correct tag, and pull in a new item, and configure it as a Gauge. It makes formatting boards a nightmare unless you use all of the default sizes.

Ability for the user to change PI Vision trend scales directly from the symbol, without having to edit on "Configure Trend".

Currently only the target attribute limit is not included when pulling attribute limits from AF limits. It would be nice for it to be included so that I can configure multistate colors based on whether or not the value is above or below the target. This would make Multistating more consistent with the Target indicator avaliable on Value and Table symbols.

It would be great, from an administration point of view, to have an option to automatically approve (new) AF databases in PI Vision.

Dear OSIsoft Support Team,

We are currently developing with WebAPI for some custom symbols in PI Vision.

We know that currently PI Vision 2020 no longer requires PIWebAPI and we would like to know if the PIWebAPI is going to be deprecated in the future or if it's a tool that is in OSIsoft roadmap for the future

If we have AF content in a test AF environment, and then we build a PI Vision display on top of that in a test environment, we have a need to migrate the AF content to a different AF hierarchy in Production. The PI Vision Display Utility is clear in the Live Library documentation that this is not allowed at this time - you may only change AF server and/or the AF database name. We would like the ability to change AF hierarchy during a display migration as well.

PI Vision's current CTP claims implementation is based off of OAuth 2.0. With OAuth 2.1 coming out PI Vision's claims implementation will need to be revised to be compliant with the new version of the framework. Specifically OAuth 2.1 is removing the implicit grant type which PI Vision requires in order to recieve tokens from the authorization endpoint of the identity provider.

When displaying a year of data from a PI point that logs data every 5 seconds, PI Visions reads all 6 million points and displays them even if it's not useful to have that precision considering that on a year trend, we won't see much of the seconds changes.
PI Vision should retrieve the PI tags in a "smart" way depending on the timeframe to be able to be more responsive and much faster! This will allow us to display 10 pi tags in the same trend over 2 years without the performance issues we have today.
Thanks

In Processbook, when we draw a trend with multiple digital tag, we can set multiple scale with the number of the state. This permit to see multiple tag with the same scale on different place in the trend. When we define the trend we see only the digital state, we do not have the choice for entering a number

Allow asset context swapping between base and derived template assets on a PI Vision display that contains multiple assets. This includes situations where a display was built for only one asset but contains a symbol with dynamic search criteria, such as a collection. When the asset context swap is configured to "Show search results", selecting a base template asset should change the context of all symbols on the display built on a derived template and vice versa.

There are no options available to customize the order of the events listed. By default the events are listed chronologically.

Currently many customers are using custom extensions to provide iFrame support to PI VIsion.

Use cases include integration with 3rd party applications (o365, Power BI, video feeds, maps, etc.)

Add an option to remove or resize the grey selection box in PI Vision. In displays where the symbols are dense and small, it can add confusion to the end users to see the selection box encapsulating adjacent symbols when they click on them.

When you input a tag/text, you have to drag the corner to resize. There is no way to define specific value for vertical/horizontal sizing. This makes it very hard to create a template file.

Is it possible to show different displays in a mosaic on the screen with an option where you can choose a template with different mosaic configurations (number and size of displays)

Please make it easy to copy the tag name off of existing trends, values, gauges, etc. This would make it much easier to share / copy tags after they have been built into an existing PI Vision screen. I know that I can get them from values, but that is difficult to do if there are multiple points on a trend.

Wish to type in indices as in chemical structure formulas, like
CH4 CO2 C2H5OH and Exponents like x^2.

The font size of trend cursor for timestamp and value is very small. Please prepare option to change the font size.

Possibility to change rights for the home folder.
Currently, anyone with publisher rights can save and share displays in the home folder, even when they only have write access on the lowest subfolder of a folder. This results in thousand displays in the home folder, making it a mess.