AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

Add a new idea Subscribe
Status No Status
Product PI Connectors
Categories General
Created by Kenneth Barber
Created on Aug 20, 2022

RELATED IDEAS

Do not silently overwrite PIPointPrefix.config.json when a PI Connector is upgraded

Currently, if you install a new version of a PI Connector, the PIPointPrefix.config.json file is silently overwritten and reverted back to the default. For users that do not use the default prefix, this means that data gets recorded in the wrong tags and not the intended tags, which, in turn, can mean that critical notifications are never sent out. In general, files that the user is intended to edit should not be silently overwritten, and files that the user is not intended to edit are safe to be silently overwritten. Please consider either making it clear which configuration files will be overwritten, either in the documentation or during installation, or do not overwrite valid configuration files.
  • Attach files
  • Gabriel Verreault
    Reply
    |     Aug 20, 2022
    @Kenneth reviewing some of the unanswered requests. This is not the behavior of the connector. The upgrade will not overwrite the PI Point Prefix. As you mention, this would cause new tags to potentially be created and break existing data flow. If you run into this issue again, please open a case with our Tech Support team to investigate
  • Kenneth Barber
    Reply
    |     Aug 20, 2022
    I encountered the issue again yesterday. I opened a tech support case for it yesterday.
  • Mic Paluszak
    Reply
    |     Aug 20, 2022
    This has been identified as a Work Item: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=5694932440781617559-340644
  • Kenneth Barber
    Reply
    |     Aug 20, 2022
    In response to Mic, I'm guessing that AVEVA has finally been able to reproduce the issue? I'm looking forward to the fix if AVEVA decides to fix it.