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.

Status No status
Created by Guest
Created on Sep 22, 2026

EntityMgmt REST API should support /data routes in CONNECT EAP

It is a common use case that users will want to query for stream store data on a given entity, component on an entity, or on the resolved entity.

In CONNECT original, REST API routes were supported to get asset data in a single request, for example ../assets/{{assetid}}/data

We should support similar routes in CONNECT EAP, to easily allow users to query stream data associated with an entity in a single REST request.

For example,

..entityMgmt/{{datastoreid}}/entities/{{entityId}}/data

..entityMgmt/{{datastoreid}}/entities/{{entityId}}/components/{{componentid}}/data

..entityMgmt/{{datastoreid}}/resolvedEntities/{{entityId}}/data



  • Attach files