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
355 VOTE
Status Completed
Product AVEVA™ PI Vision™
Categories AF Integration
Created by Ryan McErlean
Created on Aug 19, 2022

RELATED IDEAS

Support renaming of AF elements and attributes

PI Vision does not support the renaming of AF elements or attributes or the movement of them within the hierarchy. After renaming or moving these objects, symbols referencing them will show No Data in PI Vision.
  • ADMIN RESPONSE
    Aug 19, 2022
    In PI Vision 2020, you no longer need to update your displays when AF elements or attributes have been renamed or moved within the AF hierarchy. A console utility will optionally run on upgrades that update your previously created displays to support renaming. For additional information on PI Vision 2020, please see the release announcement here: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000031641
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    Just found out this is an issue.... an a big one if you have lots of displays and frequent rebuilds of the AF model...
  • Guest
    Reply
    |     Aug 19, 2022
    If you change the root element of AF structure, all your displays are automatically broken!
  • Guest
    Reply
    |     Aug 19, 2022
    Getting this fixed potentially has huge benefits in areas such as Pharma where Coresight screens may be a controlled part of a process, which in turn locks down the AF model and takes away most of the flexibility of working with and editing a tree-structure model. Any steps that can be taken by OSIsoft to make sure the AF elements and attributes can be moved around without breaking the data connections to the tools that use them (coresight, notifications, analytics, etc) is a huge plus!
  • Guest
    Reply
    |     Aug 19, 2022
    I have Changed the root Element & created new Elements. But in PI Vision all old elements are showing up with "No Data" status when placed on the display.
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Alan, please see this request. https://feedback.osisoft.com/forums/320517-pi-vision/suggestions/15040746-support-renaming-of-af-elements-and-attributes
  • Guest
    Reply
    |     Aug 19, 2022
    PI vision symbols mapping to the AF attribute through the address path string.  That data connection will "break" if any of the elements in the path are changed or relocated.  If PI vision mapped to the attribute value using the attribute and element unique IDs the PI vision display could be resilient to any changes in the AF naming or hierarchy.
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Alicia, will other clients also support the renaming of elements? I am now particularly interested in the PI Integrator for Business Analytics. Regards
  • Guest
    Reply
    |     Aug 19, 2022
    Also, PI Vision 4.x is NOT this release scheduled for Q2 2019, correct? So it should take even longer?
  • Guest
    Reply
    |     Aug 19, 2022
    This is a major issue as it blunts much of the flexibility built into AF and Vision. We have a use case where AF Elements can move to other spots in the hierarchy on a regular basis.
  • Guest
    Reply
    |     Aug 19, 2022
    We run several open pits. Part of our daily business is the adaptation of plant names to the progress of open pits. Facilities are being built, relocated and taken out of service. Each of these actions requires changes in PI-AF and PI-Vision. Most of these are renaming of the plants to depict the progress of mining. A simple way to rename elements in PI-AF and at the same time in their dependent PI-Vision displays would save us a considerable amount of time.
  • brian.e.roberts
    Reply
    |     Aug 19, 2022
    two questions ....1) is the script available for AF item moves that "break" PI Vision references?  2) does the script or other script work for PI Vision references to PI Points that have been renamed/retagged.  thanks.  
  • Guest
    Reply
    |     Aug 19, 2022
    In response to brian roberts, "two questions ....1) is the script avail..." #1: Yes, I will contact you directly to share the script.   #2: In most cases there will be no issue with PI Points since the name and PointID are both stored in the definition of the display. A tag rename is handled automatically. A tag deletion and re-creation will also work fine, if that is what "retagged" is referencing.
  • Guest
    Reply
    |     Aug 19, 2022
    Rename Attribute Name on AF and do not broken reference on PI Vision
  • Guest
    Reply
    |     Aug 19, 2022
    Rename Element Name on AF and do not broken reference on PI Vision
  • Guest
    Reply
    |     Aug 19, 2022
    Rename Database Name on AF and do not broken reference on PI Vision
  • Guest
    Reply
    |     Aug 19, 2022
    Edit AF element and do not break Pi Vision displays
  • Guest
    Reply
    |     Aug 19, 2022
    Edit AF element and do not break Pi Vision displays
  • Guest
    Reply
    |     Aug 19, 2022
    Yes, please. This would be very helpful. Working on a customer's site screens and have had to do major updates to AF based on their feedback. This is forcing me to essentially recreate many of their screens with each revision.
  • Guest
    Reply
    |     Aug 19, 2022
    PI Vision should use Elements/Attributes GUIDs instead of names so it can point to the same objects even if they are renamed.
  • Lebretonp
    Reply
    |     Aug 19, 2022
    I vote for this enhancement. We update often AF database or attribute and we don't want rebuild screen each time
  • Load older comments
  • +255