We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT 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 CONNECT data services. For links to our other feedback portals, please see RESOURCES below.
Noting that I am not the original poster for this idea, I can try to share my experiences.
When renaming an existing tag which is written to by the adapter, there is a special procedure described in this KB article:
https://softwaresupportsp.aveva.com/en-US/knowledge/details/000103249?lang=en_US
The process is quite fragile, and I cried countless tears in cases that I forgot to delete the ExDesc. I also encountered some problems that required me to restart the OMF endpoint which was receiving the info from the adapter. Likely this was something related to the cache mechanism, or maybe it was just a superstition that I developed at the time.
It would be nice to have a single interface where the Data Selection, the point name in the PI DA, and the ExDesc are all updated in a single shot.
Thank you for your feedback. We'd like to understand the exact behavior you are requesting. Are you wanting the AVEVA Adapter to change the name of existing PI tags in the PI Server? That will not be feasible, as Adapters do not have the means/permissions to modify something that has already been created in the data endpoint.
If you could share your scenario and ultimate goal with us, that would help us with determining how to best support you in what you're looking to accomplish or provide you with a solution that currently exists.