Low code/no code improvements to Numbering Schemes and VDS integration

[paulo_figueiredo_wsp]

Functionality:

Provide a user-friendly environment with no Powershell scripting to relate numbering schemes with cascading properties and discrete visibility to specific categories.

Autodesk example that exists today:

Look at the ACC solution.

You can easily create a properties using any definition you want, attach it to a numbering scheme.

The numbering scheme is not limited to 10 fields, it can be longer to fulfil international standards.

Once user selects the file name from picklist, the properties are automictically populated according to selection.

You can easily map the numbering scheme to specific folders by "tick box" process where applies, hence discrete list is offered to end-user - same concept can be adopted for categories.

No powershell required, easy adoption and agile to suit projects and product delivery.

[Frodl]

See also this idea:

Possibility for numbering schemes with mor than 10 different fields - Autodesk Community

[kerrild]

@paulo_figueiredo_wsp Did you have any success with this?
We are currently looking at implementing something like the cascading properties you have suggested. 

In our example, the user selects a descriptive word from a picklist, then the properties are automatically populated according to the selection.

By pre-selecting these properties for the user, the time-saving on data entry and the increased accuracy of data will be hugely beneficial, so it's quite a hot topic for us.

We are about to start working with a CAD Supplier to achieve this, so any feedback would be greatly appreciated. 

[paulo_figueiredo_wsp]

Hi @kerrild ,

Thanks for your message—great to hear this is a current focus for your team.

I raised this idea because I’ve seen how Autodesk Construction Cloud (ACC) provides a much more intuitive approach to document numbering and cascading properties. In ACC, you can easily create a numbering scheme that links to properties, and once a file name is selected from a picklist, the related properties are automatically populated. It’s simple to maintain, quick to adopt, and requires no scripting—something Vault unfortunately lacks.

As of now, the Vault product team has not adopted this functionality into the 2026 release, so there’s still no built-in, user-friendly solution in Vault to achieve this behavior natively.

That said, if it helps, Autodesk does offer an add-on called Vault Enterprise Add-On. It includes a Document Numbering tool where you can define custom schema definitions. If configured properly and applied by users, you can cascade the filename into property sets. However, it’s not as straightforward as ACC—it requires deeper configuration and is more complex to maintain.

I’ve been pushing for a low-code/no-code path forward, so any momentum from the user community helps build the case.