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.

PIEFDat

SUPPRESS THE COLUMN NAMES. I am working "one rwo at a time" where an attribute within an event must match something in another column, but can't do it when PIEFDat always returns two rows for each query. grrr. The older Batch system version could do all this stuff.
  • ADMIN RESPONSE
    Aug 16, 2022
    Hello Everyone, While we appreciate the community's interest in this suggestion, we have decided to decline this item in favor of other high-priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for improving PI DataLink for you! Thanks, Victor Zhang OSIsoft, Product Manager
  • Attach files
      Drop here to upload
    • sjohnson
      Reply
      |
      Apr 16, 2025

      Also disappointed this has been declined. We view this as more of a BUG FIX than a feature enhancement request. All other DataLink functions allow you to suppress headings (most don't show any headings at all.) Why not Event Frame "explore events"? We have to go through heroic efforts to work around the fact that EVERY explore event query returns at least 2 rows -- 1 for the header, 1+ for any rows of results. Seems like it would be a very simple fix that would be very useful to us.

    • Guest
      Reply
      |
      Aug 16, 2022
      YES, we need this too. We have MANY workbooks with batch where this function is used, and they are now going to be converted to Event Frames, but we need to use A LOT of time on manual rebuild because this feature is missing.
    • Guest
      Reply
      |
      Aug 16, 2022
      Hi Victor, WOW, SO SAD to hear that! If you only knew the amount of time we are using in order to convert from BatchView to Event frames, because of this simple missing feature is IMMENSE, not to talk about the looks of the results, when having 10 or even 20 Event searches on top of each other, because of the other missing features in Explore Events. Best regards An frustrated user Christian
    • Guest
      Reply
      |
      Aug 16, 2022
      Hi Christian, I'm sorry to hear that you are frustrated with the news. While we decided not to include the functionality in the coming release, the additional details of the use case provided in your comment will be useful when evaluating features to be implemented in the future. Thank you for sharing them, and please don't stop giving us feedback. Best, Victor Zhang OSIsoft, Product Manager