AVEVA™ PI System™ Feedback Portal
Welcome to our feedback site!
We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.
To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.
This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.
PI Vision can link directly to files on file-shares and local file-systems. Because of browser restrictions, likely it will be very difficult to take advantage of the feature.
This explains how to add a navigation link to PI Vision display symbols:
Add a navigation link to another display or website
https://docs.aveva.com/bundle/pi-vision/page/1009793.html
To reference a file, the UNC path https://en.wikipedia.org/wiki/Path_(computing)#Universal_Naming_Convention of the file needs to be converted to a URI https://en.wikipedia.org/wiki/Uniform_Resource_Identifier. For example “S:\pictures\tankfarm.jpeg” becomes file:///S:/pictures/tankfarm.jpeg, and \\myhost\shared_folder\tankfarm.jpg becomes file://myhost/shared_folder/tankfarm.jpg. Note that PI Vision only serves a webpage with the URI link to the file. The browser will attempt to open the file.
By default, PI Vision restricts the type of navigation links. This document explains how to edit the web.config file to override the default restriction settings:
Override the security settings for navigation links
https://docs.aveva.com/bundle/pi-vision/page/1009387.html
In the past, I have used file: URI references to files on file shares and local file systems. Unfortunately, recent versions of many browsers. including Google Chrome and Microsoft Edge, restrict access from https: URIs to file: URIs. Access to file: URIs can be enabled by domain group policy, browser settings, or browser extensions. In my environment, I was not able to make this work in a reasonable amount of time spent fiddling with settings.
It might be a tedious administration burden to enable file: URI access for a diverse population of browser users. Since PI Vision is already hosted on Microsoft IIS, it might be easier to host a website that points to a file-share with the files. Then the files can be accessed by HTTP or HTTPS URI links. The files can be maintained by replacing the files on the file-share. Alternatively, the navigation links could point to files hosted on a Microsoft SharePoint site.
If you want to proceed further, these online resources can help you convert the UNC paths to a URI:
Online UNC to URI Path Converter
https://pathconverter-pp.azurewebsites.net/
Generate "file://" URIs in Windows Explorer
https://superuser.com/questions/297060/generate-file-uris-in-windows-explorer