Version 31.5.1.0

Released on November 3rd, 2025

For information on the compatibility of each P4V version with Autodesk Vault versions, visit the System Requirements page. To download the software, visit our download page.

New features

Support for Vault 2026

Starting with version 31.5.1.0, we added support for Autodesk Vault Professional 2026.

Changes and Improvements

• The internal application structure was upgraded to fully support the .NET 8 technology required by Autodesk Vault Professional 2026.

• Changes to the availability and processing of Vault Properties (see below).

If you plan to use the Pending publication feature of the ERP Connector, a corresponding version of the ERP Connector (version 31.1.0.0 or higher) must be installed.

Update on the Availability and Processing of Vault Properties

All Vault properties with an internal ID value of 0 (e.g., Date Version Created (Date Only) and similar properties with the date/time specification in parentheses) have been hidden from all lists of Vault properties. They either returned empty values or caused publishing modules to behave incorrectly.

Instead, the ‘full’ Vault property (e.g., Date Version Created) can be used in the file name configuration, and the desired date/time format can be selected from the Date Format drop-down list.

Inventor BOM Module

Any now-hidden Vault properties used in the BOM export configuration (originating from older versions of Publisher4VLT) will be exported to CSV/XML, but their values may be empty. Properties with an internal ID of 0 will not be available in the list for newly created configurations.

Watermarks

Any now-hidden Vault properties used in the Watermark configuration (originating from older versions of Publisher4VLT) will cause the publishing job to fail with the Specified argument was out of the range of valid values error message in the job queue.

• JobPublishing/Publish: Job publishing error.\r\nInventorPublisher/PublishEntity: Job Publication Error.\r\nInventorPublisher/RunWatermarksProcesses: Watermarks process error.\r\nWatermarkBuilder/CreateWatermark: Watermarks process error.\r\nWatermarkBuilder/CreateTextWatermark: Error during create text watermark.\r\nNamingBuilderLibrary/GetPublishFileNameByConfig: It was not possible to build the name of the published file.\r\nSpecified argument was out of the range of valid values.

This can be fixed by removing the empty rows from the watermark naming configuration window.

Properties with an internal ID of 0 will not be available in the list for newly created watermark configurations.

File Naming with Vault Properties

Any now-hidden Vault properties used in the to-be-published file name configuration (originating from older versions of Publisher4VLT) will cause the publishing job to fail with the Specified argument was out of the range of valid values error before being submitted for processing.

This can be fixed by removing the empty rows from the file name configuration tab.

Properties with an internal ID of 0 will not be available in the list for newly created naming schemes.

Known Issues

• The 'Sheet as a separate file' option in PDF publishing does not work for the following publishing methods and configurations:

  • AcCoreConsole 2026 – Model and Layouts

  • Full AutoCAD 2026 – Model and Layouts

  • Full AutoCAD 2026 – Layouts

• Conversion to AutoCAD Mechanical DWG does not work in the AutoCAD DWG module when the AcCoreConsole is used.

• Not all fonts available in the list can be used in watermarks. It’s a problem with a new external library to which we had to upgrade because of .NET 8.

  • As a ‘workaround’, use safe fonts like Arial or Tahoma.