AVEVA™ PI System™ 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, 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.

Add a new idea Subscribe
Status No Status
Product PI Integrators
Categories AVEVA™ PI Integrator for Business Analytics
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

Option to delete target data table when view is deleted

When a PI View is deleted from the Integrator User Interface, the Publication Metadata and target data tables are both deleted for that view. For a view with a non-PI View target such as a SQL target, however, only the Publication Metadata table is deleted. The Integrator will no longer consider that view name to be reserved after deleting the view, but using that name again for a new view with the same target requires us to manually delete the target table if there is a change to the shape or we do not want to append to the existing data table. It would be great to have an option to decide whether to delete the target data table as well when a view is deleted.
  • ADMIN RESPONSE
    Aug 16, 2022
    Correction to earlier comment by Matt Ziegler: This idea was not fulfilled in PI Integrator for Business Analytics 2018 release. This idea is currently not planned for a future release. If you have a use case and desired behavior for a particular writer and want to discuss further, please comment below or email me. Thank you!
  • Attach files
  • Guest
    Reply
    |     Aug 16, 2022
    This feature will be included in the release after PI Integrator for Business Analytics 2016 R2 SP1 which is currently scheduled for Q1/2018.
  • Matt Voll
    Reply
    |     Aug 16, 2022
    I don't see any mention of this in 2016R2SP1 release notes nor in the 2018 release notes. Has it been completed?
  • Matt Voll
    Reply
    |     Aug 16, 2022
    In response to Matt Ziegler, "This feature will be included in the rel..." I don't see any mention of this in 2016R2SP1 release notes nor in the 2018 release notes. Has it been completed?
  • Guest
    Reply
    |     Aug 16, 2022
    I tested this out today and do not think it was implemented in this 2018 release.
  • Matt Voll
    Reply
    |     Aug 16, 2022
    In response to Laura Posner, "I tested this out today and do not think..." Thanks for checking. I am upgrading from 2016 to 2018 this week sometime.   While I think the issues presented by old tables not being deleted when the View is deleted is drastically reduced by the ability to modify existing views . . . this still presents a long term manageability concern.
  • Matt Voll
    Reply
    |     Aug 16, 2022
    i'm unsure what 'use case' you are looking for beyond the initial idea. The scenario in the idea is still a valid concern. If a PIIntegrator View to a non-PI View target (like a generic SQL database) is deleted, the corresponding Database Table remains in the SQL Database . . . which is thus confusing for users accessing the views via a SQL connection (like PowerBI). The entire concept of using Integrator adds a lot of moving parts between data in PI to data accessible to something like PowerBI . . . without then adding additional items like a dedicated PI ODBC driver and configuring a new Data Source on the users computer to access the PI Views . . . thus the reasoning with using a generic SQL target.
  • Guest
    Reply
    |     Aug 16, 2022
    Besides the SQL writer, did anyone vote for this that is using a different writer? If so, please comment! Thanks!
  • Guy Acciai
    Reply
    |     Aug 16, 2022
    IMHO, this applies to any SQL target, aka Oracle or SQL server - I can somewhat understand the need for this to be an optional setting, either associated with the specific target (Like a drop table when deleting a view checkbox), or possible even making this an option during the View creation itself (for a SQL based sort of target), but the status-quo is a mess for DB users. We did give some of our power users access to create their own PI4BA views, which in turn, creates DB tables for them. We typically give these folks RO access to the underlying DB server, to then pull their data. Obviously, the owners can delete their own PI4BA views, but the resultant DB table remains (as Pi4BA created it for them, it seems that this should be deleted, when the view that created it, is also deleted. At Bottom line, this is definitely confusing for our users, and can leave "orphaned" data out in the DB server, that requires manual effort to sort out, what's still a valid table, compared to the views still exist in PI4BA Either build this into the product, or release a separate utility (or stored procedure?) than can query AF, find the meta data about what views should be in the DB, and compare this to the actual tables in the DB, with an option to delete DB tables to get things back in sync.
  • Guest
    Reply
    |     Aug 16, 2022
    @Joy Wang: is this considered for a furture PII4BA release? I agree with Guy's comment below, it is very confusing for users and IT to be able to delete the view without deleting the SQL Table. Can you explain why this is not done? If the PII4BA has R/W rights on the server, What is preventing the service account from deleting the table? Thanks for any help you may provide --Selmane