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 Declined
Categories PI Web API
Created by Guest
Created on Aug 23, 2022

AdHoc StreamSet actions fail if there is at least one bad WebId

Currently calling any of the AdHoc StreamSet actions causes the entire call to fail if the request includes at least one bad WebId. It would be better if the response came back successful and only the sub-items with bad WebIds included an error message.
  • ADMIN RESPONSE
    Aug 23, 2022
    We have reviewed this idea, and it’s not something we plan to implement at this time. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!
  • Attach files
  • Guest
    Reply
    |
    Aug 23, 2022
    I wanted to add to this issue. The entire streamset request will also fail if any of the streams return data that isn't supported by the PI Web API. This makes it very difficult to debug in production systems because we cannot determine which stream is the culprit.
  • Guest
    Reply
    |
    Aug 23, 2022
    "we are trying to build a telemetry catalog for on-demand bulk ETL for data scientists and this request being fulfilled would allow us to remove the costly and annoying web_id verification process."
  • Guest
    Reply
    |
    Aug 23, 2022
    Kevin, thank you for reviewing this issue. I hope you will reconsider this one as in my opinion it is a pretty major bug with the web API that is preventing us from realizing the full potential of the performance improvements streamsets offer. Without a fix for this we are resorted to using only one webID per streamset, otherwise there is a potential for major data loss in our applications.