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 aclaus
Created on Aug 5, 2026

Allow Payload edits for Sparkplug B

I have devices that are outputting utilizing Sparkplug B and the current adapter is not picking up what your techs are calling the high register, so my tags are recording values of 0 instead of actual time.

Here is resolution to one of my tickets asking:
When using MQTT Sparkplug B with PI Adapter for MQTT, the Sparkplug B payload structure is predefined and the adapter automatically decodes Sparkplug messages and extracts the metrics. Because of this, JSON parsing/mapping attributes such as valueField, indexField, indexFormat, dataFields and dataType are not available in the Sparkplug B data selection/configuration. Those settings apply to generic JSON payload selections, not Sparkplug B messages, where the metric structure and datatype are already defined by the Sparkplug specification and carried in the message.

Here is another resolution to a case I submitted:
Our Adapter is limited to reading one value per metric. That is just how it is built. There is an internal desire to allow for sub-metrics in a future release, but for now, this is just how it is.

The Adapter does not support having two values under the same metric name. You will have to separate the low and high values into separate metric names on the source server, and then update the Data selection to reflect that.

  • Attach files