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
Categories PI Builder
Created by Guest
Created on Aug 20, 2022

Change behavior to retrieve contacts in bulk

In a large scale deployment, or in an undersized system retrieving AF Contacts, or accessing the subscription tab on a Notification Rule can be slow. A solution is of course to properly size the system or reduce the scale, however there is a compounding effect where contacts are retrieved one at a time instead of in bulk. Changing this behavior would significantly mitigate this issue even if the system is undersized as the call would only happen once not once per contact. This is also the case if there is a performance issue (network, etc...) when accessing AD. As there are multiple single calls, the performance issue is exacerbated.
  • Attach files
  • AlexMeade
    Reply
    |
    Aug 16, 2023

    This issue should have been addressed and optimized already. The directory wait is brutal and long each time we click on subscriptions tab - adding only one sub folder as an option dosnt work. I doubt any organizations keep all their contacts in one ADUC folder structure. Also we tested the "one subfolder" option just to test, and there was no speed improvement. This is been happening a long time now, its a huge hit in productivity when trying to tune and maintain notifications /subscriptions. - which in turn has cause a mess in this part of our notifications. Could someone please put attention to this core part of AF and fix this ?