Vault Custom Properties Not Updating After Mapping to Inventor

Vault Custom Properties Not Updating After Mapping to Inventor

bshinde3ZRN3
Community Visitor Community Visitor
64 Views
1 Reply
Message 1 of 2

Vault Custom Properties Not Updating After Mapping to Inventor

bshinde3ZRN3
Community Visitor
Community Visitor

I created a part in Inventor and checked it into Vault. I then added five custom properties within Vault. To update the values of these properties, I developed a custom Vault program that checks out the part, modifies the properties, and checks it back in. This process successfully updated all five properties.

Later, I mapped two of these Vault properties to corresponding Inventor properties. After the mapping, I created a new part, checked it into Vault, and ran the same customization program. However, only the remaining three unmapped properties were updated. The two mapped properties did not reflect the changes.

Upon reviewing the documentation, I found that mapped properties are marked as read-only and cannot be updated programmatically. I’m now looking for a way to update these mapped properties. Is there a recommended approach or workaround to achieve this?

0 Likes
65 Views
1 Reply
Reply (1)
Message 2 of 2

Markus.Koechl
Autodesk
Autodesk

Updating properties with Read (Read/Write) mappings must update the file's property values using the respective CAD API. See SDK Documentation -> Knowledgebase -> Properties on how to achieve this. This approach is complex but robust, like the built-in capabilities.

MarkusKoechl_0-1757418417120.png

There is an alternative approach, less complex in implementation, but not as robust, as it is not a native API call, but rather a library method of the Vault Client installation: IExplorerUtils.UpdateFileProperties. You can find sample code here: Vault-Sample---InventorExportAnySampleJob/Autodesk.VLTINVSRV.ExportSampleJob/JobExtension.cs at 2025.... This method performs all steps, including checkout, writing properties to the file and database, and check-in, with a single call; however, you will not be able to differentiate if one of these steps fails. In case of a partial failure, the entire call will fail. Your application's .NET platform must match the Vault Client's .NET platform: .NET 4.8 for Vault Client 2025 and earlier versions.NET8 for Vault 2026.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes