AVEVA™ Products 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, select the product of your interest in the left column. Then 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 will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status In Development
Portfolio area Historian & Client
Created by Jake Hawkes
Created on May 14, 2026

RELATED IDEAS

Refresh Tag List Enhancement in Historian Client (Process Improvement)

ADO Work Item #4784132 — Refresh Tag List Enhancement in Historian Client (Process Improvement)
https://dev.azure.com/AVEVA-VSTS/_workitems/edit/4784132

DESCRIPTION

In Historian Client, there is no option available to refresh the server or tag list. Whenever backend changes are made (for example, adding or deleting historized applications/tags), the updated information is not reflected automatically in the client.
Users are required to restart the Historian Client to retrieve the latest configuration and tag information. This results in workflow interruptions, especially in environments with frequent configuration changes.

STEPS TO REPRODUCE

Pre-Condition/Prerequisite:
1. Historian Client is connected to a Historian Server

2. Existing historized applications/tags are visible in the client

3. Backend configuration changes are performed (add/delete/update tags)

Expected Result: Users should be able to refresh the server/tag list within the Historian Client and immediately view the latest configuration changes without restarting the application.

Actual Result:
Updated tags or configuration changes are not reflected automatically. Users must restart the Historian Client to retrieve the latest server/tag information.

Additional Notes:

This limitation impacts usability.

  • Attach files