powerGate v24




  • Issue in the ERP Integration Settings dialog where changes to list values for ERP fields were not saved when Vault Data Standard (VDS) is installed.

  • Display problem in the ERP Integration Settings dialog where changing the Vault Entity Type caused the selected value to disappear.




  • Updated powerEvents to version: 24.0.12
    This fixes occasional issues with Sample.ConnectToERP scripts on Vault 2021 environments, where the Vault Client may freeze on login.




  • The ERP Integration Settings dialog now allows to configure a list of values that are allowed for individual ERP fields, when creating Items in ERP.
    Especially for the manual Item creation, this makes it easy to control which values are displayed in selection lists.
    And this also applies if some ERP values don’t directly match the data in Vault.

  • New UI component: ERPComboBox

    • displays all the configured list values for the bound ERP field

    • shows the configured DefaultValue if no ERP Item exists

    • clear error display if no suitable ERP value is configured for the mapped Vault property


  • Sample “ERP Item” tabs now display the list values in their UnitOfMeasure comboboxes, which are configured in the ERP Integration Settings dialog.
    (Sample.Tab-ErpItem.xaml and Sample.ErpItemCreate.xaml)

  • The sample BOM Window “Item Transfer” now also takes these list value configurations into account.
    (Sample.Tab-File-ErpBom and Sample.Tab-Item-ErpBom scripts)

  • Removed sample script Sample.ManagePowerGateConfiguration.ps1 and the associated configuration file Sample.PowerGateConfiguration.xml, because these are no longer relevant after the changes described above.
    (Sample.Menu-Inventor-CreateErpItem.ps1 hard-codes the original GetPowerGateConfiguration 'UnitOfMeasures' configuration)

  • Updated powerEvents to version: 24.0.11
    This fixes possible performance problems caused by too frequent Connect-ERP calls during Vault Client or Inventor startup, especially when connecting multiple slow ERP services.


  • Failing ERP item creation when mapping Vault Enum Properties such as Classification, Visualization Attachment, Property Compliance or File Link State.
    The issue was caused by New-ERPObject returning a non-transferable Autodesk. ... .PropertyDefinition+EnumeratedValue object instead of the underlying Vault value.

  • Incorrect error displays in the ERP Integration Settings dialog, when mapping numeric Vault Properties to number fields




  • The ERP Integration Settings dialog now allows to configure via mappings, how Items are created in ERP.
    For individual fields, it is now possible to specify whether data from Vault properties or fixed-values should to be transferred.

  • Extended New-ERPObject with a -VaultEntity parameter that converts passed powerVault Entities to the corresponding ERP format, based on the configured mappings



  • Vault Client crash when invalid characters are entered as powerGateServer Host Name in the ERP Integration Settings dialog

  • Display problems in the ERP Integration Settings dialog, which did not show connection settings in some exceptional situations:

    • during evaluation the used Demo ERP system was unfortunately only displayed on first opening

    • after manually importing a powerGate.settings file into Vault, the current settings are now displayed immediately, even without logging into Vault again




  • A new ERP Integration Settings dialog allows Vault administrators to configure ERP services on a Vault-wide basis.
    This enables all common powerGateServer situations as well as direct OData connections to be easily set up.

  • The Sample.ConnectToERP script automatically connects to all these configured services when logging into the respective Vault in Vault Client and Inventor

  • Extended Connect-ERP with a -UseSettingsFromVault parameter, which e.g. makes this easily possible also on the Job Processor


  • Renamed sample script Sample.ConnectToPowerGateServer.ps1 to Sample.ConnectToERP.ps1

  • Instead of the Sample.ManagePowerGateConfiguration script, now the Sample.ConnectToERP script adds a Tools menu item to the Vault Client for opening the current Vault - ERP Integration Settings





  • Updated Licensing to version: 18.3.1

  • Updated powerEvents to version: 24.0.4

    • This solves the problem where changes to ERP integration scripts being incorrectly reloaded on MTA background threads, resulting in a smoother debugging and development experience:
      Connection Error Dialogs are displayed again if problems occur with new changes in such scripts.

    • Changes can now be saved even while modal dialogs are open. It is no longer necessary to restart the Vault Client if, for example, Error Message Boxes, Connection Error Dialog, BOM Windows, Inspector dialogs or simple Message Boxes are displayed.
      Advantageously, for scripts based on our ERP BOM tab samples, changes in BOM Window functions now take effect immediately without the need to re-open the window, reloading tab contents, or waiting for any Check-operations to complete.

    • In addition, all sample ERP integration files are now installed in %ProgramData%\coolOrange\Client Customizations.

    Breaking Changes

    Change paths in Customization distribution mechanisms

    Please note that the simplification of the folder structure for Client Customizations may require adjusting paths in automatic distribution mechanisms (e.g. setups or IT tools).
    For more details, see the “Breaking Change” section in powerEvents v24.0.4


  • Issue in sample scripts for ERP BOM tabs where failed BOM row creations were incorrectly marked as successfully transferred in the BOM Window.
    BOMs are now again created with deep-create, which ensures that they are transferred as a whole and marked as erroneous, even if there are problems with the creation of individual BOM rows.


    For ERP interfaces implemented with a ERP BOM tab based on v24.0.3 or v24.0.4, it is recommended to update the section for creating BOM headers and rows in the Transfer-Boms function.




  • Issue in sample script for Inventor Menu item “Create/Update ERP Item” and Inventor Menu item “Link ERP Item” where the parent assembly was used when a part or assembly was opened within an opened assembly




  • The user interface for the “ERP Item” and “ERP BOM” tabs in the Vault Client have been redesigned

  • Added “Link ERP Item” tabs for searching and linking an existing ERP Item to a selected Vault File or a Vault Item

  • Added “Create/Update ERP Item” Inventor Menu item for creating or updating an Item in ERP using iProperties of the active Part- or Assembly-Document

  • Added “Insert ERP Item” Inventor Menu item for searching and inserting an existing ERP Item as Virtual Component or as Raw Material for the active Part- or Assembly-Document

  • Added “Link ERP Item” Inventor Menu item for searching and linking an existing ERP Item to the active Part- or Assembly-Document


  • The Sample.ConnectToPowerGateServer script is enabled by default on new environments and automatically connect to the public Demo ERP system by default

  • Renamed sample scripts Sample.TransferERPItemViaFileTab.ps1 and Sample.TransferERPItemViaItemTab.ps1 to Sample.Tab-File-ErpItem.ps1 and Sample.Tab-Item-ErpItem.ps1

  • Renamed used Sample.TransferERPItemTab.xaml to Sample.Tab-ErpItem.xaml

  • Renamed sample scripts Sample.TransferERPBOMViaFileTab.ps1 and Sample.TransferERPBOMViaItemTab.ps1 to Sample.Tab-File-ErpBom.ps1 and Sample.Tab-Item-ErpBom.ps1

  • Renamed used Sample.TransferERPBOMTab.xaml to Sample.Tab-ErpBom.xaml

  • Renamed sample script Sample.SyncERPTabConfiguration.ps1 to Sample.ManagePowerGateConfiguration.ps1

  • Renamed used configuration Sample.DefaultERPTabConfiguration.xml to Sample.PowerGateConfiguration.xml




  • Easy and secure upgrade of already productive ERP integrations implemented with v21 (or older) and Vault Data Standard, so that working can be continued as usual on all workstations


  • Updating the product disables all sample ERP integration scripts by default if they were not already present on the workstation before.
    So for v22 upgrades (or older) also all Sample.TransferERP…Tab.ps1 and Sample.SyncERPTabConfiguration.ps1 files are installed to the .\Disabled subdirectory, so they no longer need to be disabled manually for compatibility reasons.

  • Automatic display of Non-Terminating Errors:

    • For Vault Data Standard integrations, connection errors and incorrect ERP cmdlet usages or parameters are no longer displayed by default.
      This eliminates the need to disable possible duplicate messages after updating from v21 or older. Such errors are now clearly displayed only in powerEvents-based integrations (and PowerShell IDE’s).

    • In powerEvents-based integrations the automatic display of these errors can be suppressed for individual ERP cmdlet calls by passing -ErrorAction SilentlyContinue


  • Issue with Updates on Job Processor environments (and workstations with unsupport Vault versions) when only main components (Cmdlets and .NET Library) were installed, but simple setup executions incorrectly installed sample files and powerJobs Client

Breaking Changes

Setup argument renamed and value changed
The Setup argument for installing only the main components (Cmdlets and .NET Library) has been renamed to MAIN_COMPONENTS_ONLY and the required value was changed to 1.
Therefore updates on Job Processor environments (and workstations with unsupport Vault versions) should be performed using the adapted command-line argument:



"\\path\to\networklocation\powerGate24.0_Vault2024.exe" -silent ACCEPT_EULA=1 VAULT_ERP_INTEGRATION=0

"\\path\to\networklocation\powerGate24.0_Vault2024.exe" -silent ACCEPT_EULA=1 MAIN_COMPONENTS_ONLY=1

Vault Data Standard integrations for v22.0.1 and later - automatic Error display removed
ERP integrations implemented with Vault Data Standard (e.g. powerGateTemplate based projects) do not contain any additional error checking or handling logic after ERP cmdlet invocations.
So that non-terminating connection errors (v22.0.1) and incorrect ERP cmdlet usages (v23.0.1) are not swallowed, the following line should be added after importing the powerGate module:

Import-Module powerGate
$global:Host.PrivateData.OnNonTerminatingError = $global:deprecated_defaultErrorBehaviorForVDS

Note: Earlier VDS integrations implemented for v21 or older, should already contain the required error handling logic and are therefore not affected (see “Autodesk Vault Data Standard - Non-Terminating Errors”).




  • Added support for Vault 2024

  • Updated Licensing to version: 18.2.29

  • End User License Agreement (EULA) has changed

  • Updated minimum required .NET Framework version to 4.7

  • Removed DEPRECATED support for simple updates of ERP interfaces that are compiled against the 20.0 version of the .NET library.
    The policy files for v20 versions of the powerGate.Erp.Client assembly are no longer installed in the GAC, which requires a rebuild against the latest version.

Breaking Changes

Projects targeting .NET Framework versions lower than 4.7 :
Projects using the powerGate .NET library that target a lower .NET Framework version than 4.7 need to be upgraded to target at least 4.7 to compile when referencing the latest powerGate.Erp.Client assembly.