When adding a record to a change order from the change order records tab, the "Look For:" option always defaults to Files. This is annoying for those managing Items via the change order as this always needs changed to Items. Suggest that rather than alphabetizing the list, that Vault remembers user last selection or otherwise gives user option to set a default for the record type to be added.       Show More

Minor fix that should be JDI.   Make the Vault Admin User Management list jump to letter on keypress. (Groups too)   For example. I want to go to users starting with "J" in my user list. I press J on my keyboard.   Bonus points if you add a text filter box.   (I'm using Vault Profession 2024-latest)   Show More

In windows "Shift delete" will allow you to delete files files without these files going to the Windows Trashcan. We need this function for the Vault Trahscan. Show More

Currently, when performing a Copy Design on a drawing (.idw / .dwg) that references multiple models, the source used to auto-generate the new drawing's filename depends on the selection order in the Copy Design interface. This non-deterministic behavior frequently leads to drawing renaming errors when multiple referenced models are involved (as also highlighted in community discussions: Solved: Re: Copy design - drawing reference mistake - Autodesk Community ). To ensure consistency and eliminate manual workarounds, we propose adding a configurable option to Vault Copy Design: Deterministic File Naming Source: Introduce a setting/rule where the drawing's name is automatically dictated by its primary referenced model (specifically, the first model inserted into the drawing, or the model that populates the main title block data). Administrative Control (Distributed / Centralized Rule): Allow administrators to set and enforce this behavior globally (or via Rule Sets) across the organization, ensuring end users cannot accidentally override the naming standard during copy operations. Business Impact / Value: Prevents Human Error: Eliminates dependency on the order in which files are highlighted or selected in the Copy Design UI. Consistency: Ensures drawings are always named predictably and remain aligned with their main model/assembly. Efficiency: Reduces time spent manually renaming or correcting mismatched drawing references after a copy action.   Best Regards Svein-Erik Show More

  Provide Regular Expressions (Regex) as an additional comparison condition for Lifecycle Transition Criteria. Currently, transition criteria allow basic property comparisons such as “is” and “is not”. For many workflows, these comparisons are too limited when property values need to follow a specific format or pattern.   An additional condition should be available: is is not matches regular expression optionally: does not match regular expression The administrator could then define a regular expression as the comparison value.   Make Regex Available for Other Property Comparisons Regular Expressions should not be limited to Lifecycle Transition Criteria. The same comparison capability should be made available wherever applicable in Vault when values are compared or filtered, particularly for: Lifecycle Transition Criteria Vault Searches / Advanced Find Other property-based filters and comparisons This would provide a consistent way of performing advanced string matching throughout Vault. Show More

Vault uses the CRC32 checksum to detect changes in files which has 4,294,967,296 possible values.  This seems like a huge number, but when you consider a system with a million files each with 10 or more versions, the probability of a CRC32 clash becomes highly probable.  In addition, some softwares have been known to abuse the CRC32 checksum resulting in frequent duplication.   Currently, when Vault recognizes that the checksum hasn't changed during the check-in process, it cancels the upload without warning to the user.  I'd like to suggest that the user instead be prompted with a dialog box that warns the user that the file queued for upload has the same checksum as the existing file in the Vault.  This dialog box would give the user the ability to force an upload if desired.   Alternatively, Vault's algorithm could consider the CRC64 instead of the CRC32 or consider both.  The CRC64 has 1.8 quintillion possible values. Show More

Hi Team,  In a future update, provide an option to exclude the Recycle Bin folder when detecting duplicate names. Many Thanks PM     Show More

We are using Autodesk Vault Professional 2026 including Vault Thin Client.   Vault currently provides a built-in Log File Configuration which automatically manages: Console Logs Server Logs File Store Logs Email Logs Audit Logs However, the following log types are currently not affected by this configuration: restapilog-* VGLog-* VaultConnectorLog-* According to Autodesk Support, there is currently no native setting to limit the retention or automatically delete these log files. As a result, Vault administrators must implement their own Windows Scheduled Tasks or custom scripts to manage these logs, while other Vault log types are already handled by the built-in configuration.   Requested Enhancement Please extend the existing Log File Configuration so that: restapilog-* files are included in the cleanup process. VGLog-* files are included in the cleanup process. VaultConnectorLog-* files are included in the cleanup process. Alternatively, provide separate retention settings for these log types. Benefits Consistent log management across all Vault-generated logs. Reduced administrative effort. No need for custom cleanup scripts. Prevention of unnecessary disk space consumption. Better support for environments using Thin Client, Vault Gateway and Vault Connector. Current Workaround Currently administrators must create their own scheduled cleanup tasks to remove old REST API, Vault Gateway and Vault Connector log files, while all other major Vault log types can already be managed through the built-in Vault configuration. Vault administrators should not need custom scripts for some Vault log types while other Vault log types are already managed by the built-in Log File Configuration. Show More

  Vault currently locks an entire numbering scheme after it has been used, including its predefined-list values. This makes it difficult to maintain a numbering structure that is otherwise intended to be stable.   For example, a scheme may use a predefined list: EP EX Existing files may already have numbers such as: 1001EP001 1001EX001 Later, a new class such as  TC may be introduced. Adding TC to the existing predefined list would not alter any existing file numbers or change the scheme structure. It would simply permit future files to use numbers such as: 1001TC001   Please allow append-only additions to predefined lists after a numbering scheme has been used. Vault could continue preventing edits and deletions of existing values, while allowing a new unique value to be added after validating that it cannot create a duplicate file number.   This would preserve numbering integrity and history while allowing organizations to add new part classes, finishes, or other controlled codes without creating new numbering schemes every time. Show More

In Inventor, "Save Copy As" already exists and as the name implies saves a copy of the currently active file as a new file.   "Save copy as" in the Data Standard tab has the same name but acts more like an Export tool to save the active file in a different file format. (CAD, PDF, etc.) To minimize confusion I think "Save copy as" in Data Standard should be renamed to "Export" or "Export as" Show More

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

Administrators would like better readability for the assignment rules. The text for the rule criteria is difficult to read – see image.   Show More

I our Vault, we have >350.000 items in the item master. Just like in the forum post below, we added file properties, mapped them, added them to categories. Assign/update item then does not create this new property in the existing item. Quote: We recently created a couple of new file properties. The properties are mapped and assigned correctly to their respective categories. All new Items populate with the properties as expected. The issue we have is updating existing Items with the new properties. Even after the new properties have been added to the file. The only way we have been able to populate an existing item is to manually add the property to the item. Our thinking was that an Item would show the new properties after being updated, but It isn't working that way. Is there an easier way to get the property in the Item without adding it manually to each Item? Source: Update existing Item with new property    The proposed and accepted solution is to manually add the file property to all existing items, in growing batches.   Our proposal for Ideastation: Can the "Assign/Update item"-fuction not be extended? Check if all mapped file properties exist. If not: add them to the item, and fill them with the mapped value. Then manual updates, and also hopefully: state changes on the jobserver, automatically result in complete items, without missing properties. Show More

Distributed views should also be made available for the CopyDesign dialogs Show More

I would like the ability to organize this list (Item Master and Project Explorer) in alphabetical order or even turn on and off options not being used.  Thanks   Show More

Hello,   When using Replace in Vault, the parent files receive a new version with the system comment:  Replace ($/Designs.ipj) It would be much more helpful if Vault recorded the replaced file names with some details, example : Replaced file 00002.ipt, version 10, with 00015.ipt, version 3. ($/Designs/Personal Projects)   This would make assembly history easier to understand without having to compare versions. Show More

It would be great if all checked-out files were displayed in Vault Thin Client as they are in Vault Pro. The files should also be crossed out.     Show More

There are large file-types, such as .step or .ifc that consume large disk-space, because they are stored as plain text. As far as I know, these files are vaulted as they are, meaning, that they will be stored in vault with just their original size. (prove me wrong, if I'm mistaken). Usually, such files can be compressed very well. If you compress such a file type, a .zip will only be a fraction of it's original file-size. Wouldn't it be helpful to have a switch in the vault-configuration to compress such files before storing them into vault and decompress them, when getting them from vault? Especially when generating lots of step- or ifc-files automatically with a jobserver, this could significantly save server storage. Show More

Please add the ability to create and save custom views across all Vault interfaces that display properties. This would be especially valuable in History, Uses, Where Used, and Edit Selected Properties, where users could customize column layouts and quickly switch between saved views. Show More