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
Product PI Integrators
Created by Guest
Created on Aug 16, 2022

Allow Configuration of Target Table Name from View for PII4BA

We have a use case where there is a need to publish data from one PI Integrator instance to multiple environments for IT to run through their dev / test / prod on the datalake setup. Our targets are SAP HANA instances, but this problem applies to all targets as it is inherent in the setup of the Integrator that the table name created is the same as the view name. Right now this requires the view names to change between targets and the view name is the name of the database table that is created. I would like to see either: 1. the database table name to be configurable 2. uniqueness constraint to be View name + target and not just view name. I believe option 2 would be the easiest to implement as you could just check the 2 together to make sure the combination is unique. With configurable table names, you might end up with name collisions unless you the Integrator checks those for uniqueness in the same fashion of table name + target.
  • Attach files