If we use a numbering scheme with a centralized number generator, we can't rename the IPT and its linked IDW at the same time because it will get two different numbers. We would need to be able to do an automatic rename for the IDW based on the same principle as the design copy. Show More

Dear Autodesk Team, when renaming a top-level or nested assembly, users often need to rename related subassemblies and parts to maintain consistent naming conventions. Automatically including all child components would greatly simplify this process. Description: Currently, when using the Rename Wizard in Autodesk Vault, there is no option to automatically include all child components (subassemblies and parts) of a selected assembly. This means that users must manually locate and add each subassembly and part to the Rename Wizard if they also need to be renamed. This can be very time-consuming and error-prone, especially for large and deeply nested assembly structures. Requested enhancement: Please add an option in the Rename Wizard to automatically include all child components of the selected assembly, similar to how the Copy Design wizard loads the full structure. For example, a checkbox such as: "Include all child components" or "Load full assembly structure" Benefits: Saves significant time when renaming assembly structures Reduces the risk of missing components Improves workflow efficiency and usability Makes the Rename Wizard more consistent with the Copy Design workflow Thank you for considering this enhancement.   https://forums.autodesk.com/t5/vault-forum/rename-nested-assembly-in-autodesk-vault-include-all/m-p/14005759#M52760 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

Currently, markups in Autodesk Vault are stored as entity attributes linked to the DWF version. These markups are separated from the markups created in the online viewer within Fusion Manage (FM). A valuable enhancement would be the ability for Vault to store markups directly in the Vault database instead of saving them only as image files. This would allow markups created in Vault to become accessible and reusable within Fusion Manage, enabling a common review and collaboration workflow across both systems.   Current Situation Vault markups are stored as entity attributes on DWF versions Fusion Manage online viewer markups are handled separately Vault currently stores markups only as image files No shared markup repository exists between Vault and FM Requested Enhancement Extend the Vault markup functionality so that: Markups are stored directly in the Vault database Markup data can be associated with Vault entities and DWF versions Markups become accessible from both Vault and Fusion Manage Shared collaborative reviews between Vault users and FM users are possible Benefits Unified review workflow across Vault and Fusion Manage Better collaboration between engineering and downstream teams Centralized markup history and traceability Reduced duplication of review comments Improved lifecycle and change management processes Consistent markup visibility independent of client application Use Case Engineering teams review CAD data in Vault, while project or change management teams review the same data in Fusion Manage. Shared markups would allow all stakeholders to work on the same review annotations without maintaining separate comment systems. This would significantly improve connected workflows between Vault and Fusion Manage environments. 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

Current behavior In Autodesk Vault, markups are attached to a specific DWF visualization version. For example: Version 13 contains engineering review markups. The drawing is later revised to Versions 14, 15 and 16. When opening the latest version (Version 16), there is no indication that markups exist in Version 13. To review those comments, users must: Open the visualization. Manually switch between visualization versions. Continue searching until they find the version containing the markups. For drawings with many revisions, this becomes inefficient and discourages the use of digital reviews. Proposed solution Instead of requiring users to manually search through visualization versions, Vault could provide a Markup History panel. Example: Visualization Version Markups Status Version 16 0 ✓ Version 15 0 ✓ Version 14 2 ⚠ Version 13 8 📝 Selecting a version would immediately display its markups. Additionally, Vault could provide an option to display all historical markups while remaining on the latest visualization. Additional improvements It would also be useful if Vault could display: Total number of markups. Reviewer name. Creation date. Markup status (Open / Closed / Resolved). Filter by reviewer. Filter by status. Jump directly to the corresponding visualization version. Benefits This would: Reduce time spent searching previous visualization versions. Improve engineering review efficiency. Encourage wider adoption of digital markups. Improve traceability of engineering feedback. Enhance the overall user experience without changing the existing markup workflow. Example workflow A drawing is currently at Version 16. During Engineering Validation, reviewers created markups on Version 13. Today, another engineer opens Version 16 to check whether all review comments have been addressed. Instead of immediately seeing that Version 13 contains review comments, they must manually open previous visualization versions until they locate them. A simple indication that Version 13 contains eight markups would eliminate this unnecessary search and significantly improve the review process. Why this matters Digital reviews are one of the biggest advantages of Autodesk Vault. However, if users must manually search historical visualization versions just to locate review comments, many teams eventually return to PDFs or paper-based review workflows. Improving the discoverability of markups would make digital reviews faster, more intuitive, and more attractive for engineering teams.   Note: The attached image is an AI-generated conceptual mockup created with ChatGPT. It is provided for illustrative purposes only and does not represent an official Autodesk interface or planned feature. Show More

This applies to all software help guides, not just Vault.   With a new release of any software or update comes a list of fixes and known issues. However, the help guides only provide a vague description followed by a SFDC Article code with seemingly no way to find this article if a user wanted to get more information.   Instead those should be links taking the user directly to the article.   The Autodesk website should also be updated to find these issues more easily.   There should also be a way to subscribe to notifications of new pages and page updates for each software so users are aware of newly found issues and fixed issues immediately instead of googling around hoping to find an existing article if it exists. Show More

In Vault 2025 Thick Client and Thin Client, the integrated Autodesk Viewer shows the “Display Edges” option, but it is disabled or has no effect for Inventor IPT/IAM files. This makes technical review difficult compared with Inventor’s “Shaded with Edges” display. Please enable visible model edges for Inventor files in the Vault integrated viewer, or provide an administrator/user setting to force edges visibility by default. Show More

Hello.   If you could please add a way to edit File Names & File Properties at the same time, it would be a huge efficiency gain and help with preservation of information. This would also help with encouraging file migration for users switching from a Windows Explorer environment to Vault or from migration of alternate competitor programs.   I think this could be achieved in  2 ways: 1) Allow changing of file name in "Property Edits". The area for editing the file name is currently greyed out and locked.     2)    a: Allow rename, copy, and paste in the Rename Wizard.        b: Allow descriptions/fields to be COPIED and then pasted into the file name rename space. I believe this would be the least             effective, but easiest way to allow copying of data between columns to the file name.   Let me know if you have any questions or other considerations. Show More

When using the Rename fuction currently in Vault, there is no way to select all dependent files for any .iam or .idw files unless all .idw's .iam's or .ipt's are moved into the same folder.    Just like how the "Change State" function can grab all related files to change a predefined lifecycle state, I think that this function would benefit the Rename function greatly, and would save people a lot of time. Especailly if their company has requirements on specific folder structures.    Show More

Autodesk Vault is able to add permission for Read/Write/Delete/Download. It will be good if users for Autodesk TC will have permission to View preview of file (Autodesk Viewer of PDF/dwf) but if they don't have download permissions option for downloading should be disable for them. Now if users permissions are configured for only read permissions, then can't view preview of files and getting error:   More details form Autodesk support:   Show More

I would like the ability to use the Job Processor to publish PDF files of office documents. This would allow us to attach released documentation of our products to their corresponding items ready and approved for internal/external use.   Our organisation has 2 user groups for the Vault. Design Engineers - Using Vault Professional and non-design engineers, sales, planning, production and purchasing using Vault Office. The second group is starting to notice the security and relative ease we manage our files. We have fully integrated Vault's Project Folder, Item Master and Engineering Change Orders into our product lifecycles. We now want to expand this to additional design documents such as:   Product Brochures Product Datasheets Product FMEA Internal/ External assembly/installation instructions   As well as QHSE documents: Norms Procedures Workflows etc.   All these files have a revision system which is currently managed by hand. We would like to transfer these files into the vault and attach the released (.pdf) versions to corresponding Items. Show More

In Inventor there is the possibility to set parts or assemblies to reference. Reference parts or assemblies won’t show up in your parts list and that’s great.  However, in the Vault Plot Manager there isnt a option to deselect drawings from reference parts/asm. Sure, in many cases reference parts won’t have attached drawing, but in many cases they have. For example if parts of your assembly isn’t sold to the costumer.  Why would you want to print drawings nobody needs? The manufacturing site is irritated because they have drawings, they dont need and its time consuming to sort out drawings.    I am the only one?       Show More

VAULT allows us to find where an IPT is used. That being said, if the IPT has Model States, there is no way to know where a specific Model State is used. This could be helpful to find if a part is OBSOLETE or not or which IAM to open if you make a significant modification to only 1 of the model state.   The other way around could also be useful. Figuring in which Model State an IPT is used, without having to open the inventor file and look at the EXCEL spreadsheet Show More

Hallo Vault-Admins, dear Autodesk-Team, for administrative Tasks in Autodesk Vault it would be very helpful to have possibility to map one or more properties within Vault to another Vault-Property or user-defined-Vault-Property (UDP). Nowadays it is nacessary to use Vault Data Standards, API or a mapping within Inventor (ILogic, Macro or definitions in the IProperty-Task). I think it should be possible to define such Property addings in Vault! In this case we only have to map one property instead of 2 or 3 to get the same result. This is, I think, an essential function for data management softwares and we should have a simple possibility to make such things. For new Vault Projects we often can find a loop way to do this. For PSP-Vault-Migrations it is an difficult work to get every possibility of mapping running.   Here an example:   We have 4 Properties and want to set 3 of them to the fourth of the properties (= summary).   Property 1: "NR.1"  (string)--> Value = "12" Property 2: "NR.2"  (string)--> Value = "20" Property 3: "NR.3"  (string)--> Value = "35.758" Property 4: "customer part Name" (property set):                          --> the result of the Property Mapping should be: "122035.758"                         --> Value = <NR.1><NR.2><NR.3>   Example 2:   We take the same Property examples as above and we want to add a limiter in between the Properties.   Property 4: "customer part Name" (string):                          --> the result of the Property Mapping should be: "12/20/35.758"                         --> Value = <NR.1>/<NR.2>/<NR.3>   There should be a simple way to configure such mappings in the Property-tab of vault Administration in the property Definition window.       Pleas vote 🙂   Thanks Dominik     Show More

By opening a drawing after making a revision and check out, nowadays the properties have to be updated by hand. Only after executing the ''updated properties'' command, the revision number and the revision table are being updated.   In my opinion there is no situation that you want to avoid the properties are being updated after executing the check out command. So updating properties should be executed automatically after check out. Show More

My idea is Email Notifications hyperlink on file open file in thin client Now Email Notifications hyperlink open file in Vault client My idea is opportunity Email Notifications hyperlink open file in thin client I have many user only with thin client and want when click hyperlink in email open file from thin client. Show More

There should be a way to retrieve different revision levels of an item in an item BOM, similar to model revisions in Inventor's Vault tree.           Show More