Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT 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 CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

Add a new idea Subscribe
Status Tell us more
Product AVEVA™ Adapters
Categories AVEVA Adapter for OPC UA
Created by Guest
Created on Jul 10, 2025

RELATED IDEAS

OPC UA Adapter: support Namespace index change after OPC UA Server restart

AVEVA adapter for OPC UA should support changes in the Namespace index that can happen after an OPC UA Server service restart.

Currently, if the Namespace index of the source signals change, the adapter stops receiving data for every point in that Namespace. The only way to fix this is reconfiguring manually the data selection, editing the Namespace part of the "nodeId" for each item.

The OPC UA adapter should be able to get the updated namespace indexes from the namespace table in the OPC UA server, without having to edit manually the configuration.

  • Attach files
  • Admin
    Jiyeon Hwang
    Oct 21, 2025

    Thank you for your feedback. I'd like to better understand in what scenarios you'd expect the Namespace index to change. AVEVA Adapters are simple data collection products where it looks for either predefined information (ie. Data Selection configuration) or stream information based on Discovery output, in order to relay data to the appropriate data endpoint(s). At the moment, we don't expect to apply refined logic in the adapter to be able to detect when NodeIds change, but it would be good to understand your exact scenario.

    Reply