Idea is to have Base34^4 & Base34^5 file naming / numbering sequence as an embedded native option in Vault. This would enable a user to pack a very large Qty of unique file names in a very short code, which would result in drawings & references being a lot cleaner & simpler & make unique files ID's easier to articulate to a consumer of designs.   A Base^34 numbering system is just like decimal (Base^10), except instead of having 10 symbols (0–9), it has 34 symbols. Base^34 uses: 0 1 2 3 4 5 6 7 8 9 A B C D E F G H J K L M N P Q R S T U V W X Y Z ‘I’ and ‘O’ are skipped so they don’t get confused with 1 and 0.  34^4 means  34 x 34 x 34 x 34  = 1,336,336 So a 4-digit Base^34 number can represent 1,336,336 unique values. (For comparison:4 digit 0000-9999 only has 10,000 unique values) 34^5 means  34 x 34 x 34 x 34 x 35  = 45,435,424 So a 5-digit Base^34 number can represent 45,435,424 unique values. (For comparison:5 digit 00000-99999 only has 100,000 unique values).  Each position in a 4 or 5 digit code can be one of 34 values.  Think of it like a car odometer that has 4 or 5 rows & each row has 34 values instead of 0-9. At last count a year ago, our Vault had 106,631 Inventor files, which took roughly14 years to accumulate, so in theory, Base34^4 could potentially last us another 175 years without being exhausted. Show More

In Autodesk Inventor with Vault, Content Center parts are stored in folders depending on the active language setting (e.g. "de-DE", "en-US").   As a result, identical standard parts can be distributed across multiple language-specific folders in Vault.   Use Case: In many companies, multiple language configurations are used (for example German and English installations of Inventor). This leads to the same standard components being created and stored in different folders based on the language setting of the user who placed them.   This causes: - Duplicate Content Center parts in different folders - Content Center parts can not be checked in if duplicated names are not allowed  - Increased maintenance effort - Difficulties in enforcing a consistent Vault structure - Complications in downstream processes (e.g. ERP, numbering, classification)   Proposed Enhancement: Provide a way to control or standardize the storage location of generated Content Center parts, independent of the Inventor language.   For example: - Define a fixed target folder (e.g. always "de-DE" or a neutral folder) - Override or map language-specific folders to a single common location - Allow consolidation of existing Content Center parts created in different language folders   Benefits: - Avoid duplicate standard parts caused by language differences - Ensure a consistent and maintainable Vault structure - Simplify data management and reduce errors - Improve integration with ERP and company standards   Look also at this idea: Lock Content Center language - Autodesk Community Show More

Copy Design Go To Button should close the Copy Design Dialog Show More

In the transition rule from WIP to Review, we have Vault set to update the dwf and pdf. We also have the files set to follow the parent. During the transition, the pdf updates and changes to the same state as the parent, but the dwf does not; the dwf should follow the rule. It does not make sense to me to leave the dwf's in WIP. Please see attachments. Show More

Vault 2027 now extracts physical properties from Inventor files, with one caveat: This only works with new Vault installations, not upgrades as defined here:   https://help.autodesk.com/view/VAULT/2027/ENU/?guid=INV-PHYSICAL-PROPERTIES Configuration requirements The physical properties, Area, Mass, Volume are available by default in newly created Vault 2027. For a restored or upgraded vault, you should manually create Area, Mass, Volume properties and map them to Inventor properties.   This should be an automatic process for upgrades as well, and not to force users to the potentially mind-numbing manual process, when this data is needed to be shown in items.   My apologies, if I have duplicated an existing post. Show More

Hello   According to your documentation only Windows 2022 Server OS is supported with Autodesk Vault Server (< ver 2027). That OS is soon out of support from Microsoft and we would like to upgrade to Windows 2025 OS using our current Vault server edition.    Anyone using Windows OS 2025, already? Other supplier often state OS version xx and above...    Best regards, Fredrik Show More

Standardize Log In/Sign In between Vault Thick Client and Vault Thin Client.  Or allow Admin to configure Sign In page for users.  Confusion with users set up with active Windows Account try to enter credentials and are denied.    Show More

The aim is to obtain a link from a PDF generated from a drawing (idw) so that Vault recognizes the connection between these files and takes this into account when checking in or checking out. Ideally, there would be a setting when exporting the PDF that says “Pin to Vault” Yes/No. I would be very grateful for any feedback. Show More

Product and Version Autodesk Inventor Professional 2025.3 Autodesk Vault Professional 2025.4 (Issue observed in multiple prior versions as well) Summary When a user makes temporary, experimental edits to a part or subassembly within the context of a parent assembly—without checking out and without saving—there is no way to discard those in-memory changes and reload the component from disk without closing all parent assemblies that reference it. This significantly impacts productivity for users performing "what-if" analysis or exploratory design changes. Detailed Description Use Case Engineers frequently need to test design ideas before committing to them. A common workflow is: Open an assembly from Vault (all files in Released state) Edit a component to test an idea, declining checkout prompts since this is temporary Evaluate the change in the assembly context Decide to discard the experimental change and revert to the released version Current Behavior The experimental changes exist only in RAM (not saved to disk) The following Vault commands do not discard in-memory changes: Refresh File — compares local disk timestamp to Vault; since nothing was saved, disk file is already "current" Get Revision — same issue; local copy already matches Vault Revert to Latest — designed for disk-level discrepancies, not in-memory state Closing the part window does not release it from memory because the parent assembly still holds a reference The only current solution is to close the entire assembly (and all of its parents), losing any valid work in progress at the assembly level Technical Root Cause Inventor's document management keeps referenced documents in memory as long as any parent document references them. The Vault add-in's refresh commands compare disk timestamps, not in-memory state. Since unsaved experimental changes never touch the disk, these commands see nothing to refresh. From Autodesk's own API documentation: "If a document is closed, the document is not really closed unless that was the final view and the document is not referenced by any other open documents." Business Impact Impact Area Description Lost productivity Users must close and reopen large assemblies (potentially 100,000+ components) just to discard a small experimental change in one part Risk of data loss If the assembly has valid unsaved changes, users face a difficult choice: lose their real work or keep the unwanted experimental changes Workflow friction Discourages exploratory design and "what-if" analysis, which are critical for innovation and optimization Training burden New users expect "Refresh" or "Revert" to work intuitively; current behavior is confusing Proposed Solution Add a new command accessible from: Right-click context menu on components in the Model Browser Right-click context menu in the Vault Browser Vault ribbon Command Name (suggested) "Reload from Disk" or "Discard Changes and Reload" Expected Behavior Prompt user to confirm: "Discard all unsaved changes to [filename] and reload from disk?" Internally close the document (with SkipSave) Re-resolve and reload the document from the local workspace file Update all occurrences in referencing assemblies Trigger an assembly update to reflect the reloaded geometry Integration with Vault When Vault integration is active, an additional option could be offered: "Discard Changes and Get Latest from Vault" — combines discarding in-memory changes with fetching the latest version from Vault in one step Scope Should work on parts and subassemblies Should work regardless of Vault lifecycle state Should preserve assembly constraints (geometry should be identical if reloading the same version) Workarounds Attempted (All Unsuccessful) Workaround Result Refresh File (Vault) No effect — disk timestamp unchanged Get Revision (Vault) No effect — local already matches Vault Revert to Latest (Vault) No effect — same reason Close part window Part remains in memory due to assembly reference File → Manage → Refresh (Inventor) Compares to disk timestamp; no reload occurs Replace Component with itself Does not force document reload Related Autodesk Ideas Submission This request aligns with existing community feedback: https://forums.autodesk.com/t5/inventor-ideas/reload-model-in-assembly/idi-p/12476534 Additional Notes This limitation has been observed and reported by multiple users across Autodesk forums dating back to at least Inventor 2020 The issue affects both Vault and non-Vault users, though it is particularly painful in Vault environments where files are often read-only and exploratory edits are common A similar "Reload" function exists in other CAD systems (e.g., SOLIDWORKS, Creo) and is a commonly expected feature Show More

Rather than starting the command prompt and using "Connectivity.vaultpro.exe resetdialog location" It would be nice if we could have a button/feature in the software we are using (Inventor, AutoCAD, Civil3D) in the menu or one of the ribbons to reset all the dialog locations to the screen the software is currently being viewed on. Hotkeys for this feature as well would make it even easier to find hidden prompt screens. Show More

Hello  The core principal of the idea is that Check-In must never fail. Enforcement moves after Check-In. Vault currently violates a foundational rule of transactional systems,  It attempts to judge validity before it records existence. By design, Vault should not decide whether engineering work exists. Its first responsibility is to capture reality, not to approve it.   Check in must be an unconditional, atomic transaction that always creates a version. Lifecycle rules, permissions, references, and automations must not block data capture. Restrictions belong to promotion and release, not to version creation. Vault should flag invalid versions instead of rejecting them: lifecycle non-compliant broken references failed jobs Jobs may fail. Files must not.   Autodesk positions Vault as a single source of truth, yet today it behaves like a gatekeeper. A source of truth records first, judgment comes later. Vault should act as a ledger, not a judge. Thanks Dan   @ihayesjr  @Richard.Rankin          Show More

Duplicate the entire folder—including all subfolders, the top-level assembly, subassemblies, parts, and drawings—preserving all links, while excluding any files referenced by the assemblies that are stored outside the folder. basically, copying top-level assembly to another folder with linking out of the folder parts (like content center). Show More

Would it be possible to make the icon for both disabled users and groups as ghosted out in the User and Group Management?   It would make it far easier for a Vault user to visually differentiate between enabled and disabled users and groups. This would be very handy when you have a large number users in the database of and don't have to open the properties of each item to see if it is disabled or not.   See attached for illustration. Show More

when editing the quantity of the item in the bill of material section of item master, you input a numerical value, but as soon as you have finished editing this and move on, the field becomes alpha-numeric, as the word 'each' gets added to the end of the value. this is terrible from an export point of view as there is already a field for the 'units' that we can automatically put next to the quantity field, so that it reads well, but when it comes to export, I can end up with '4 each' 'millilitre' as the columns sit next to each other, this is going to require post-processing in excel or something in order to make that work for import into and ERP/MRP system. it seems very messy to have something editable as a numerical value, and then to have the software take that away from me and convert it into something i don't want and can no longer use. I've got customers who are being put off adopting the Item Master because of the small bumps that can be easily fixed, and this is a prime example of that.     Show More

Description: Currently, Autodesk Vault does not provide an option for obfuscation of CAD data or sensitive design details. Obfuscation is critical for organizations that need to share files externally while protecting proprietary information, intellectual property, and confidential design elements. Benefits of Obfuscation in Vault: Enhanced Security: Prevents unauthorized access to sensitive geometry or metadata when sharing files. Compliance: Helps meet data protection and IP security requirements in industries like automotive, aerospace, and defense. Controlled Collaboration: Allows external vendors or partners to view only necessary details without exposing full design intent. Reduced Risk: Minimizes chances of reverse engineering from shared files. Show More

The DataStandard window is very large for us (2025-10-19 00_06_28-DataStandard_Standard.png). With smaller monitors, you can no longer confirm the "Okay." We would like to create a multi-column window. (2025-10-19 00_06_28-DataStandard_new Design.png) ------------------------------------------------------------ Das DataStandard Fenster ist bei uns sehr groß(2025-10-19 00_06_28-DataStandard_Standard.png). Bei kleineren Monitoren kann man das "Okay" nicht mehr bestättigen. Wir würden gerne das Fenster mehrspaltig aufbauen.(2025-10-19 00_06_28-DataStandard_new Design.png) Show More

The DWF Viewer functionality (https://aps.autodesk.com/viewer-sdk) - just for local dwf data from dms instead of uploading every model zu autodesk-servers. A Viewer on premise. Like in Thin Client, just without Vault-Credentials.. Show More

Hi,   In vault, I have noticed sometimes the settings are changes silently that impact other users. For examble, if the enfource unique files option in removed by other user who have access that's suppose to notify all users. Similarly, all the settings change for vault setting or global settings to be notified via email should be a great feature. I am using vault pro. 2025 FR. Glad to hear a solution in the patch updates shortly if possible!   Thanks, Mohamed Rafick S Show More

We have users who generate artwork for our products, packaging we would like to store these "design files" in our vault to keep track of all our design data needed to produce a product / packaged product in one place.   Since the web client does not allow users to check in files they don't have a solution and we have to use complex work-arounds to get the data into the vault. Show More