Several of our customers work with AutoCAD in combination with Vault Professional.   Current behaviour When a DWG file is renamed via the Vault Rename wizard, the "Update Part Number" option is only effective for Inventor files. For AutoCAD DWG files the option is not applied, so the Part Number keeps the old value after the rename. According to Autodesk's own support article, this is expected behaviour in the current product state: "Update Part Number" in the Rename Wizard only works for Inventor files, while other file types such as AutoCAD or Microsoft Office documents do not have the same functionality. As a result, users have to correct the Part Number manually after every rename. This is easy to forget and leads to inconsistent data — for example duplicate or outdated Part Numbers in BOM exports and in downstream ERP systems.   Requested behaviour Extend the "Update Part Number" option of the Rename wizard so that it also works for AutoCAD DWG files: when a DWG is renamed, the Part Number is updated to match the new file name and written back into the DWG, in the same way it already works for Inventor files. Ideally this behaves as an option the user can switch on or off per rename operation, consistent with the existing dialog.   Prerequisite The Vault property "Part Number" is mapped to a property of the DWG document (property mapping configured in the Vault Behaviors / property mapping settings).   Benefit No manual post-processing after renaming AutoCAD drawings Consistent Part Numbers between file name, Vault property and DWG content Reliable BOM and ERP data for mixed AutoCAD / Inventor environments Consistent user experience across file types in the Rename wizard Show More

It would be helpful if the user received a notification in Inventor indicating that they are not currently working with the latest project file from the Vault. Especially in large environments, you don’t always want to have to notify 300 (or more) users that they need to double-click the project file because a change has been made. Show More

This is a copy of an old (archived) Vault idea. We have several clients looking for this functionality, so that's why I decided to bring it back. https://forums.autodesk.com/t5/vault-ideas/data-standard-integration-for-microsoft-office-amp-vault-office/idc-p/13783393#M13501 Data Standard integration for Microsoft Office & Vault Office Thick Client I recently saw a demo of M-Files. I wanted to hate it, being a Vault proponent. But it's really good, they have nailed what data management for the end user should be like.    Data Standard goes some way towards improving that for CAD users, and frankly could be molded to very closely match the M-Files setup at the front end. But Vault is lacking some of the back end M-Files has, since it uses a different approach. Any way, what set it apart most clearly from Vault was a form based UI everytime an Office user created a new document. It asked a series of questions and requested input of values into properties before the user could start to build their new document.   There were two approaches; Create a new file using M-Files within Word, or Save a normal Word file to the M-FIles drive in My Computer.    Either way the M-Files form appears.    This is almost identical to the way Data Standard works in AutoCAD and Inventor. It would be really good to see this functionality extended into Office as part of Vault Office, Workgroup & Professional. Then non-CAD users can be sold Vault solutions instead of needing to purchase an additional SQL based document management system for the rest of the company.   Often management can relate to needing a document management system, but fail to understand or balk at the costs associated with getting one for their Design / Engineering departments. This type of functionality would be a door opener for increasing the number of companies moving from Vault Basic to WG / Pro or even buying it from the outset.     Show More

Idea Summary: Enhance the Vault Data Standard Add-In for Inventor so users can edit and assign properties to multiple parts or subassemblies at once, using a table-like interface similar to Excel.   Problem Description: When working with large, nested assemblies that include many parts and subassemblies, managing file properties (iProperties / Vault properties) one by one is extremely time-consuming. Currently, Data Standard only allows editing a single file at a time — which means repeating the same process dozens or hundreds of times for every component in a complex model. This limitation slows down workflows and increases the risk of inconsistent metadata across a project.   Proposed Solution: Add a multi-file property editor within the Data Standard Add-In that allows: Viewing all related files (parts and subassemblies) in a grid/table view. Editing and assigning properties for multiple selected components simultaneously. Copying and pasting property values across rows, similar to Excel. Applying predefined templates or rules to several files in one step. Validating changes with existing Data Standard rules before committing them to Vault.     Show More

I'd like to disable a specific Vault command in a menu in Inventor Professional 2026. How to reach the menu: load a file in Inventor, go to Vault tab → Show Details → select a tab with a file list, such as "Uses" → right‑click file. Here I want to disable the "Assign/Update Item" context‑menu command. The reason is that the user doesn't accidentally run the Autodesk out-of-the-box command, and thus break the business process and/or the CAD structure metadata. We have our own custom Assign/Update Item commands. Along with disabling UI access, disabling should also prevent any access to it via APIs. Show More

When we create a plant layout in Inventor (or any other large assembly) we often struggle to check that new top-level assembly into Vault due to it having what Inventor sees as an unsaved change or “dirty” file. This caries on after the initial check in with every subsequent check in making it very frustrating to check it in later. Most of the time the files that Inventor sees as "dirty" are because they are sub-assemblies with flexible positional representations, these assemblies are also in a released state so we couldn't check them out to save them anyway.   This causes our team working with very large layouts a lot of headaches. Most of the time that team will only have the very top-level assembly checked out as that is the only file that they need to edit. For initial check in we have been forced to check in an empty assembly with the name we want and then saving over the top of that so we can fool Vault to let us check it in. For subsequent check-ins we have been getting around this partially by either saving the files out of turn or saving only the top level that is checked out and then closing the assembly so we get the prompt to check in on close. This works most of the time (80%) but when it takes up to 30 minutes to open an assembly to just close it again to check it in, we lose large amounts of productive time! This also doesn't work if you have other assemblies open and just want to update the layout in the Vault.   We need a way of being able to check in just that assembly regardless of the state that Inventor thinks its children are in. If all the child files are the latest version in the Vault I can’t see why this isn’t possible. Show More

The current Rename Wizard in Autodesk Vault is functional, but quite limited in everyday use. To significantly improve usability and efficiency, I would like to propose the following enhancements: 1. Non-blocking Search & Replace Window Currently, the “Search & Replace” window blocks the Rename Wizard and the Vault main window. Problem: No simultaneous access to Vault data during renaming Texts or file names cannot be easily copied and reused Re-running searches or comparing names is cumbersome Suggestion: The Search & Replace window should be non-modal (non-blocking) Allow users to work in parallel by: Navigating within Vault Copying file names or text Flexibly building and adjusting search/replace patterns This would significantly speed up workflows and make the process much more intuitive. 2. Extended Rename Functionality (similar to “Joe Rename”) The current Rename Wizard only offers very basic functionality. Problem: Complex renaming tasks require multiple passes No support for combining rules No dynamic elements (time, counters, etc.) Suggestion: Introduce an advanced, rule-based renaming system with combinable functions, such as: Combinable Operations Search & Replace (existing but should be expanded) Add prefix / suffix Remove or extract substrings Change case (upper/lowercase) Dynamic Elements Insert date/time (e.g., YYYY-MM-DD) Automatic counters (incremental numbering) Custom placeholders Multi-step Processing Multiple rules applied sequentially Full preview before execution Preview & Validation Live preview of new file names Collision detection (duplicate names) Warnings for invalid characters Benefits of These Improvements Significantly more efficient batch renaming Reduced risk of errors through better preview features Less need for external tools A more modern and flexible user experience Conclusion: By introducing a non-blocking UI and a more powerful, rule-based renaming system, Autodesk Vault could greatly improve usability and productivity—especially for power users and environments with large datasets. Show More

Use AssemblyLoadContext Internally Within Vault Add-Ins  With Vault 2026+ using .NET 8 (& the separated .NET Core version of 2025), there is no separate execution context for the add-in to run. So, if there is a NuGet package/assembly version conflict with the add-in and Vault or another add-in, it will cause an error. Below are some resources for how to do this manually within each add-in.   Could this be built into the standard 'IWebServiceExtension', 'IExplorerExtension', & 'IJobHandler' to prevent the need to do this manually?   Blog article on Vault add-in implementing AssemblyLoadContext: https://tylerwarner.dev/assemblyloadcontext-for-vault-addins   Sample Vault add-in implementing AssemblyLoadContext: https://github.com/tylerwarner33/autodesk-vault-assembly-load-context   Blog article on Vault add-in implementing AssemblyLoadContext via a NuGet that updates the IL code at runtime: https://tylerwarner.dev/assemblyloadcontext-for-autodesk-addins-with-isolatorfody   Sample Vault add-in implementing AssemblyLoadContext via a NuGet that updates the IL code at runtime: https://github.com/tylerwarner33/autodesk-vault-assembly-load-context-fody   Revit implementation discussion about internal implementation: https://feedback.autodesk.com/project/forum/thread.html?cap=cb0fd5af18bb49b791dfa3f5efc47a72&forid=%...   Accepted Inventor idea for the same internal implementation: https://forums.autodesk.com/t5/inventor-ideas/use-assemblyloadcontext-internally-within-inventor-add-ins/idc-p/14004748#M52374 Show More

Users would like to be able to configure a timeout for Autodesk jobs. The reason is that DWF jobs can run for a very long time (up to 1...2 hours) and then abort with an error. During this time, the job processor is blocked and cannot process any jobs. If it were possible to set a timeout of 15 minutes, then a job would abort with an error and would not block the job processor. The faulty jobs can then be restarted by the administrator in the evening and it doesn't matter how long they run. Show More

Hello. Please Unify UI icons, UX and style for Check Out / Check In / ... dialogs. As you can see from image below, left dialog is from Inventor-Vault add-in and the right one is from Vault Client.       Best regards, Rene Repina Show More

With the VDS in Inventor, no properties (standard and user-defined) can be displayed or edited if a function is assigned to them. Additionally, if a standard (non-custom) property is set through a function via the VDS, a new custom property is created with the system name of that property. I'm attaching a video of the behavior. A new file was saved for the first time and a value was written to the comments. The Comments property then became a function that additionally displays the Test property. When opening the data sheet, the Comments property is no longer displayed. If you write a new value there, the user-defined Comments property is created.   In versions 2021/2022/2023 and 2024, this behavior can also be reproduced with Win10 and Win11.   It is desired that the VDS can display and edit properties with a function in the same way as properties without a function. It would certainly make sense to adapt the interface similar to that in Inventor and add the "fx" button next to the properties that are defined by a function, to change between the functions definition an its output. Show More

It would be very helpful for users if the state glyph could be displayed in the properties in the Vault Browser.   Show More

it is not possible to use  Revit User Propertys im Vault for write in Revit Projekt Information for Example.     Also it is not possible to Use Revit Property in System Vault Property Show More

At the moment there is no possibility to check if the Inventor drawing is updated with its model´s latest (geometric) version.   It would be nice to have any flag, where you can see, if the drawing is, so to say, fully updated. In certain cases, somebody is updating the model and forgets to update the drawing. In other words it should be checked, may during changing the state to released. Customizable of course in the life cycles.   Note: Check over the check in date is not possible, because on the one hand the model is newer, on the other hand the drawing is newer, but not opened in Inventor. Could happen during state change.   Please provide any possibility to check this situation. Show More

There are two great features in Inventor and Vault. Unfortunately, these cannot be used together.   In Inventor fx rules can be stored for properties so that this property can be composed of other properties. In the Vault, you can define that a property requires a value.   Unfortunately, this cannot be used in combination, as a property with an fx rule is not displayed in the Data Standard. For example, the property "Title" requires a value and is filled in Inventor using the fx rule. After pressing the save button the Data Standard not display this property and the save button (OK) is not released. The required value is missing for the Data Standard if an fx rule is set.   Please allow these two great features to be used together.   1. Screenshot - property with fx rule                   2. Screenshot - Data Standard (title is missing)                           3. Screenshot - No fx rule                         4. Screenshot - Title is shown correctly     Show More

Hello,   i think Autodesk should integrate automatic PDF-Publishing into Vault (2D-PDF) like the DWF-Publishing.   The DWF is more powerful and Autodesk want to spread it with force, but there are some reasons for the PDF format:   - PDF is an ISO-Standard, DWF not. - You can open DWF only on Windows, there is no DesignReview form MAC or Linux. - The DWF-Viewer works only on prozessores with SSE2, PDF-Viewer are running everywhere. - Everybody has installed an PDF-Viewer, DesignReview normaly nobody without Autodesk Products.   Best regards   Michael   Show More

I propose to increase the difference in color between icons "The file is locked and the local copy is up-to-date" and "The file is locked and the local copy is not up-to-date." Currently, in practice you can not see the difference.     Best regards Jakub Show More

Hi,   I would like to request support for using themes (Dark, Light) in the Vault DataManagement Framework contrlols like the VaultBrowserControl and the RevisionDropDownControl. Of course it would be helpful as well to be able to 'forward' the theme colors to other regular Windows Forms controls as well. Show More

Many of our customers use Vault Data Standard for the input of properties in a Vault context. Currently though, all input I do in the Data Standard form is written into the primary model state. It would be great if we could use the Data Standard interface also for secondary states. Of course that makes no sense when I have a new model and save it for the first time. But later, when I start the command “Datasheet”, the form should pull its entries from the currently active model state. And, when I change entries, they should be written into the currently active state. The frosting on the cake would be if the whole thing also honours the toggle between editing a single state or all states. Show More