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 Declined
Created by Guest
Created on Aug 19, 2022

Support string values in formula data references

Formula data references do not support string value type attributes (e.g. if stringattribute="Yes" then "X" else "Y"). One workaround is to create an analysis on the element template with the same logic mapped to an attribute on the element template. In certain cases, however, an analysis will not work. For example, for an event frame with manually-entered string data individual to each event frame that then determines the value of another event frame attribute based on IF/THEN logic), we need this value to be calculated per event frame and not on the element.
  • ADMIN RESPONSE
    Aug 19, 2022
    We currently have no plans to extend Formula Data Reference to support strings. As the name implies, the original intention of Formula DR is to perform simple mathematics.
  • Attach files
  • Guest
    Reply
    |
    Aug 19, 2022
    Yes our clients have error codes which are not necessarily numbers and are stored as strings. We do need to write an IF-ELSE block using string type attributes.
  • Guest
    Reply
    |
    Aug 19, 2022
    I am hesitant to upvote this.  I certainly believe we should offer something to fill the need.  Not so sure that the Formula DR is that something.  I would rather see Asset Analytics changed to allow a simple Expression analysis on an event frame.   If the input strings are fixed and well-known, I would consider placing them in an AFEnumerationSet, if possible.  You may use AFEnumerationValues in a Formula DR but admittedly it is a bit ugly since you must hard-code the numeric values.
  • Guest
    Reply
    |
    Aug 19, 2022
    In response to Rick Davin, "I am hesitant to upvote this.  I certain..." Agree Asset Analytic on Event Frames is cleaner approach and if that would have been there this would perhaps not be required.
  • Guest
    Reply
    |
    Aug 19, 2022
    I believe having string operations in formula DRs can significantly increase the modelling flexibility of AF. We were faced with the problem of requiring to execute operations involving strings at the Attribute/subattribute Level for a variable number of attributes in certain elements. Writing an Analysis DR for every Attribute was certainly not a feasible approach. The problem could be easily solved by more advanced formula DRs (supporting strings) or alternatively with role up Analysis deploying custom functions (not only the current sum, add, etc). The latter is also a feature we would be interested in having.
  • Guest
    Reply
    |
    Aug 19, 2022
    I disagree with that last point Mr. Kwan. The name "formula data reference" does not imply that strings cannot be referenced. If my element has string attributes, I expect the Formula DR to be able to reference them, if not as input operators, than as outputs at least. Even ye olde PI Performance Equations support string functions. Very rough first day of learning PI-AF running into this altogether unexpected and rudimentary behavior. Why is Attribute Value Type: String even allowed in combination with Data Reference: Formula? I wasted hours trying to figure out what *I* was doing wrong. I hope you give this request some reconsideration.