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

Search results

Showing 4 of 4

Ua Server force failover / improve failover logic

Let me preface this by saying that I know it is a workaround for a non-compliance with the OPC UA specifications. The point is that the situation described below is unfortunately all too common and the workaround is needed. It often happens that t...
Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 1 No status

Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs. When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the v...
Randy Giguere over 1 year ago in AVEVA™ Adapters / General 0 No status

Provide additional time formatting options for RDBMS Queries

Background: Today we are collecting data from our AspenTech IP21 Server thorugh the PI Adapter for OPC UA and the related AspenTech OPC UA Server. This works perfectly fine for analogue data but not for data which is providing us equipment status ...
Hans-Otto Weinhold over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for RDBMS 1 Tell us more

Don't change product version information response structure

The design of the /productinformation response has changed between EDS 2020 and EDS 2023 Patch 1. Our application missed the new position of the version string so I had to change code to catch it. I know the product has shipped so there is nothing...
Guest about 2 years ago in AVEVA™ Edge Data Store / General 1 Declined