Skip to Main Content
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.

Status No Status
Categories General
Created by taterhead247
Created on Aug 23, 2022

Import-AFXml (PowerShell) should have ContinueOnError option

Both AFImport.exe and ImportXml (AFSDK) have options to continue on error (like is something is checked out or if there is a duplicate element name). For some reason the PowerShell version doesn't. This should be added.
  • Attach files
  • Guest
    Reply
    |
    Aug 23, 2022
    There is a common powershell parameter called ErrorAction. Unfortunately setting this to SilentlyContinue, Continue or Ignore results in the import stopping and a check-in of some new objects and other objects are left in a checked out state. If ErrorAction is not defined, the import stops and does an undo check-in. Perhaps this common parameter could be implemented properly to solve this request. As a workaround, I'm using the powershell cmdlet start-process to start the afimport.exe.
  • Brent Bregenzer
    Reply
    |
    Aug 23, 2022
    You can also load AF SDK directly into PowerShell and use the export method. For examples, see: https://pisquare.osisoft.com/s/Blog-Detail/a8r1I000000GvdCQAS/improving-af-backups And https://pisquare.osisoft.com/s/Blog-Detail/a8r1I000000GvEwQAK/exporting-af-databases-using-powershell