topic [Vault Data Standard 2026] - Properties binding issue in Vault Customization Forum

[Vault Data Standard 2026] - Properties binding issue

John_G. — Wed, 06 May 2026 13:22:05 GMT

Hello everyone,

I used to modify XAML and PS1 files on VDS context a few years ago.
Mapping properties seemed quite simple and could edit presentation and still bind properties :

While updating to 2026 Autodesk products, i tried customizing VDS and find out that it behave weird.
Vault mapping seems well configured and AutoCadDynamicProperties.xml file seems okay too.

1- When setting a value in default "Comments" field, the file does checkin in Vault but the value is not set, i have the same issue for custom fields. Even tried with default XAML and PS1 but have the same result, only properties in Dynamic properties Grid does update.

2 - After typing a value in a TextBox field (let's say "Designation"), when you enter another field, the Designation field get empty again.
Still using Binding like this, is it still okay ?

In @Markus.Koechl "VDS-Sample-Configurations-2026-master", it appears that Binding is sometimes different "WPF:ValidatedBinding", do you know what is the difference with previous Binding ?

For now, only manage to make it work properly by using default Dynamic properties grid :

3 - With PS1 file, in function InitializeWindow, when i manually set a value to a field, it actually doesn't set the value :

$Prop["_DESIGNATION"].Value = "TestValue"

I could only make it set the value by setting the value refering to the field like this :

$dsWindow.findName("txtDesignation").Text = "TestValue"

Do you know how to do these two things the right way ?

Best regards,
Jonathan

Re: [Vault Data Standard 2026] - Properties binding issue

Markus.Koechl — Mon, 04 May 2026 10:11:58 GMT

Which Vault version targeted your legacy customized version?
ValidatedBinding isn't new to 2026; it's been available for many years. Depending on the origin of your dialogs, there are other reasons your dialog might fail.
The good thing is that the default configuration dialogs using DynamicPropertiesGrid obviously work. E.g., if your customization is older than 2025, I suggest starting with the new default templates and transferring your customizations to them instead of updating the existing ones. You can find detailed steps on how to migrate customized configurations here: https://autode.sk/4l1Znm3 (targeting 2024 -> 2025.3), https://autode.sk/48z0Ugc (2025 -> 2026), and https://autode.sk/3Q5Boc2 (2026 -> 2027).

Re: [Vault Data Standard 2026] - Properties binding issue

John_G. — Mon, 04 May 2026 10:18:04 GMT

Hello Markus,

It used to be with Vault 2022.
But here, i already started from scratch, my custom files are based on 2026 default template files.

Thank you, will take a look to these pdfs

Re: [Vault Data Standard 2026] - Properties binding issue

Markus.Koechl — Mon, 04 May 2026 10:49:06 GMT

OK, glad to see that you started fresh with 2026. Then, the documentation on how to migrate is less relevant.

Why would you prefer having static fields and the effort of maintaining them instead of leveraging the dynamic grid?

If you have good reasons (they exist, don't get me wrong) to continue with static fields, the VDS Tutorial Chapter 07 may help you understand the requirements for adding static fields to a form: Vault Help | Chapter 07 - Extend Datasheets - Static Properties | Autodesk.

Re: [Vault Data Standard 2026] - Properties binding issue

John_G. — Mon, 04 May 2026 15:18:44 GMT

The only reason for not using dynamic grid is that it's for a customer, they are used to an existing form on Inventor, i try to replicate it through VDS.

I went back to your tutorials yesterday but unfortunately it didn't help.
Simple case, restored template files, added a TextBox field, that binds with a User defined property, in the grdGeneralProps Grid but :

If i bind with Text="{Binding Prop[MyProp].Value}", i can type a value in that field but the value disappears as soon as i select another field.
If i bind with Text="{WPF:ValidatedBinding Prop[MyProp].Value}", i can't type in that field, like if it was readonly or disabled.

I just don't understand what i'm missing here.
It feels like when you try to bind a property, it is protected/read-only, except when using dynamic properties grid.

Re: [Vault Data Standard 2026] - Properties binding issue

John_G. — Thu, 07 May 2026 15:18:59 GMT

Hello,

My bad, in Autodesk Vault 2026 Documentation :
https://help.autodesk.com/view/VAULT/2026/ENU/?guid=GUID-9851FE4D-6788-467F-B79D-EF78F385BD2C

Just find out that User defined properties used in VDS should not be prefixed with underscore character.
Otherwise, the property is considered Read-only and causes previously specified issues.

Thread is solved.