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 Declined
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Exclude AF UOM when exporting library objects

In PI System Explorer, when using "Export to File..." and with "Include All Referenced Objects" selected, please allow one to exclude UOM's from the XML file.  Due to the UOM database being server wide and not just for AFDB. 
  • ADMIN RESPONSE
    Aug 19, 2022
    Unfortunately there are potential issues with both scenarios. If a database doesn't include UOM, when it is imported into the destination, someone has to either use the UOM at the destination and make adjustments as necessary, or risk the potential for wrong day, such as Formulas or Analyses. Therefore by enabling this idea, we can inadvertently create other issues. As such, we have no plans to implement this idea at this time. Our recommendation is for both source and destination to have the same UOM conversions.
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    This is very important when we are working with different AF Servers (ex: one development and the other one is production). Sometimes the development database is located at the system integrator office, and not necessarily the conversion factors would be the same across the 2 databases. With the option you suggested, we avoid "polluting" the production database, making sure it remains intact. If a specific UOM is needed, the user would simply import it in a separate xml file before importing the full xml file with the option "Exclude UOM" set. Today, I manually have to delete the UOM section of the XML file to avoid contamination of the production database during a deployment activity.