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

Status No Status
Categories General
Created by Randy Giguere
Created on Dec 7, 2023

Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs.

When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the value of a field and we can't make use of the text parser or jsonpath xpath for stream names and Ids.

For example the current payload:

[

{

"Asset": "Truck01",

"Speed": 10,

"Status": "Operating",

"Time": "2023-12-07 00:10:00Z"

},

{

"Asset": "Truck02",

"Speed": 13,

"Status": "Operating",

"Time": "2023-12-07 00:10:10Z"

},

{

"Asset": "Truck03",

"Speed": 0,

"Status": "Stopped",

"Time": "2023-12-07 00:09:00Z"

}

]


The data selection will need to contain an item for each truck and attribute and the value of the Asset cannot be used to dynamically name and Id the stream. Furthermore, if a new truck is added to the payload, it will need to be added to the data selection, the data selection will not dynamically add the streams based on the payload pattern.

This is a feature that is available in a product such as PI Connector for UFL.

These adapters should probably use a similar logic for data selection to the one used for the UFL connector.




  • Attach files