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 Search
Created by Ryan Biggins
Created on Aug 16, 2022

Optimize tag search by introducing a setting allowing less precision when filtering a tag search by value (especially for float tags)

For example, when searching for Float32 tags with a value of -0.062 in PI System Management Tools, several results may appear, whereas no results appear in an equivalent tag search in PI DataLink. The value of the tag in PI SMT may display as -0.062, but further investigation (such as looking at archived values with piconfig) may show that the true value is -0.06245. Searching for tags with this exact value in PI DataLink returns all expected. A valid request would be to allow PI DataLink to apply the same rounding rules (or display digits tag attribute, if that's what's occurring) to the search that PI SMT tag search does. Perhaps this can be a setting that could be toggled. The use case is that the value may appear as -0.062 in PI ProcessBook or PI Vision, and so an end user that is prohibited access to administrative tools like piconfig may be confused when searching for a tag with this value, not knowing that it is not the actual value. Additionally, wild cards appear not to work in the value filter field. The current workaround is to search for an example tag that is known to contain the value and hover over it to get the full value from the tool-tip in PI DataLink. However, this does not work if the user does not know of an example tag that would contain the value of interest prior to performing the search.
  • 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