Skip to Main Content
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.

Status No status
Created by Paul Kim
Created on Aug 19, 2022

In a string builder DR, allow use of substituted values from non PI point DRs to retrieve an attribute value

If I have two AF databases, I would like to pull the value of an attribute from one database to another. The string builder path for the other database's attribute requires a value substitution from a non PI point DR from in the target AF DB (which where I want to bring the value). However, AF does not allow me to do this and the value of my string builder DR is the exact path (including the substituted values) I require, but does not bring in the value I need. For example, I have two AF databases with data of interest: //Electric City/Meters/Meter_12345678|Data Archive The attribute Data Archive indicates the name of the Data Archive which contains the PI point DRs for the asset Meter _12345678 I have another database where I need this string value of Data Archive within: //Electric City/Billing/Accounts/0123|Data Archive The following is another attribute and its value: //Electric City/Billing/Accounts/0123|Meter ID and Meter ID is a string of value Meter_12345678 For the following string builder DR for the attribute //Electric City/Billing/Accounts/0123|Data Archive, I would like to use following configurations to pull the value for Data Archive in: //Electric City/Meters/'Meter ID'|Data Archive However, the final value is observed in PSE is the expected path(//Electric City/Meters/Meter_12345678|Data Archive), but does not actually pull in the value from the other database.
  • Attach files