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

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

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

We (at coolOrange) do a lot of iterative configuration work against customer requirements — build a vault, apply a configuration, test it, adjust, repeat. Today the two operations at the heart of that loop are UI-only in the ADMS Console: Export Configuration and creating a new vault from a configuration file. Everything either side of those two steps is already scriptable. Connectivity.ADMSConsole.exe covers backup, restore, defragment, purge, migrate, library attach/import/export and filestore validation.  The DTU gets us the ability to load a fully developed Vault from a metadata package. The Web Services SDK gets us most of the way on the object model. But the moment we need to stand up a fresh vault from a known-good configuration, a human has to click through the console — which means it can't live in our build scaffolding, and the configuration itself can't be meaningfully version-controlled alongside the rest of our work. The ask is simple: give us either CLI operations for creating a vault from a configuration file and exporting a vault's configuration (-Ocreatevault / -Oexportconfig / -Oimportconfig, or whatever fits your switch conventions), or an aggregated administrative API surface that covers the same ground, so we can drive it from PowerShell or .NET. Either would do. We're not asking for anything the console doesn't already do — just a non-interactive way to reach it. The payoff for us is that vault configuration becomes a source-controlled artifact we can diff, review and roll forward, and spinning up a disposable test vault stops being a manual chore. I'd guess we're not the only shop doing repeatable configuration work who'd use this. Happy to elaborate on our specific workflow if it's useful. Thanks, @milt  Show More

  Vault Lifecycle Transitions currently support actions such as revision bumping, property synchronization, validation checks and Job Server tasks. However, there is no native way to automatically update Vault properties during a lifecycle transition. For example:     Pending Eng Validation ↓ Eng Validated     Vault should be able to automatically set properties such as: Eng Approved By = Current User Eng Approval Date = Current Date/Time This would eliminate manual updates, improve traceability, and avoid the need for custom Job Processor development or third-party add-ins for a common engineering workflow. Suggested dynamic values could include: Current User Current Date/Time Current State Previous State Revision Static Value This would make Vault Lifecycle workflows significantly more powerful while remaining simple to configure. Show More

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

To support differential updates of downstream applications, please add filter for lastModifiedDate for items and files endpoints. Alternative: Support it with a header (if-modified-since) like in Fusion Manage REST API. https://help.autodesk.com/view/PLM/ENU/?guid=FLC_RestAPI_Advanced_Functionalities_item_details_endpo... 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

It should be possible to assign different default distributed views to different vault groups Default View X | Group X Default View Y | Group Y 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

We are moving to full Azure and would like to associate 'Autodesk ID' to all existing Vault users. I don't think there is a way to do this with 'Import Updates' option, but would be nice to have this automatically accomplished. Show More

Hi everyone, It would be very helpful to have the option to control the visibility of the Quick Search tool. This is how it looks by default:  Ideally, there should be an option to keep it permanently like this:  The reason is performance: in large vault environments, the default Quick Search can significantly slow down the vault server. In contrast, searching using multiple properties leads to much better performance and a smoother experience.       Hallo zusammen, es wäre sehr hilfreich, die Sichtbarkeit der Quick Search steuern zu können. So sieht sie aktuell standardmäßig aus:  Wünschenswert wäre eine Option, sie dauerhaft so darzustellen:  Der Hintergrund ist die Performance: In großen Vault-Umgebungen kann die standardmäßige Quick Search den Server deutlich verlangsamen. Die Suche über mehrere Eigenschaften hingegen verbessert die Systemleistung spürbar und sorgt für ein flüssigeres Arbeiten. Show More

Dear Autodesk,   In our Vault environment, we use both numeric and alphanumeric values for the Position Number in BOMs. However, Fusion Manage restricts this field to integer values only, which prevents a complete and accurate synchronization of these values. Additionally, due to the current design of the Vault Connector, it is not possible to map the Vault Position Number to an alternative field. We kindly request the enhancement of the connector to allow mapping of the Vault Position Number to a custom BOM property in Fusion Manage.   Thank you for your consideration. Show More

Hello.   Thin Client Viewer Model Tree Search enhancement to Select All found occurrences is needed.   When we search for specific component in the model tree and find several similar occurrences, sometimes we want to see them all where they are installed, so "Select All" (Highlight All) would be great, because currently our assembly colleagues have to search that 1 by 1, which is a big time wasting for no reason.     Similar idea station problem: https://forums.autodesk.com/t5/vault-ideas/thin-client-quot-find-quot-function-enhancement-same-as-in-quot/idi-p/14049184     Best regards, Rene Repina 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

Don't know if this was already posted. I know this functionality from other PDM Systems and I am wondering why Vault does not check for uniqueness for a property-value.  We are checking this with DataStandard and we can also get a list of items if duplicate entries have been found, but a standard build-in functionality for all Vault Objects would be much better. E.g.: In Procad's Profile PDM System it is just a checkbox that can be set for each Property and during a user-entry the field gets highlighted if the value has been entered before. Show More

Gang....we would like to see an archiving enhancement similar to what the Purge command has. Rather than archive entire files or projects, we would like to archive versions of files. Once files reach a certain date, only keep 3 versions for every file in Vault.   Here are the thoughts behind my wish.... Our Vault is 20+ years old (5.6 TB file store), and we have never purged. We keep every version that has been checked in since day one, and the main reason is for proving it out when someone infringes on our IP. We can go back and prove that we had these designs in process. It has helped us numerous times over the years when in litigation. We know patent laws change and keep changing... but we still would like to hang onto this IP.   So, with the addition of archiving in VP2026, we would like to archive those versions instead of permanently deleting them?   The Purge functionality is exactly what we need, and it works. The problem is that we don't want to permanently delete that old legacy data just in case we need it someday.   The only option we have right now to reduce our file store is to take a backup before we start Purging and store it away. When that time comes, and we need it, restore the data to a temp server.   Best, Steve Hilvers   Show More

In Fusion Manage, all lengths of cut material assigned to a single element lose their production information regarding the cut length.   AirSystemAssy.iam in Inventor Inventor Main Assembly AirSystemAssy.iam with Tube & Pipe. Inventor BOM with different Quantities: -QTY (with pipe or tube part length) -Item QTY (Quantity without length mostly each) -Base Unit (with Each, in, mm) Inventor Structured BOM: AirSystemAssy.iam in Vault Assembly File Structure in Vault with all Subassemblies and Parts: Vault Item BOM: -Quantity, Unit Qty, Units und Item Quantity Fusion Manage BOM after synch with Vault Connector 2026.2 Fusion Manage AirSystemAssy BOM with tube & pipe parts:     Solution for the problem: Why not design the Vault Connector so that it displays the instances as BG and the stock number (stock tube) with the length below it?     Once you switch to the Flat Bom, you'll even have the sum of the lengths.       Show More

Use case : Our design projects exist of well organized, large projects, which we call Programs and which contain several smaller Work Packages (WPs). For example: Program X WP_A – Pre-study phase WP_B – Permit Drawings & Plans WP_C – Design Drawings Phase A WP_D – Railway Station Construction Models WP_E – Design Drawings Phase B ... All drawings, references, and Data Shortcuts are managed in Vault and enriched with metadata. This allows different user profiles to efficiently search, query, and group files across the entire system, regardless of whether they need information within a specific Work Package or across the entire Program.   Current configuration : Our Vault configuration is designed so that the Program represents the Civil 3D Project for Data Shortcuts. This approach is necessary because “Cross-Work Package collaboration” is only possible when the Program level is defined as the Civil 3D Project. Data Shortcuts are shared across multiple Work Packages. Mapping individual Work Packages as separate Civil 3D Projects would prevent this cross-Work Package workflow.   Issue : While this configuration works well for Data Shortcuts, it creates usability issues in Civil 3D. Designers use the Vault Projects section in the Civil 3D Toolspace to browse drawings and Vault Data Shortcuts. Because the entire Program is presented as a single project: The lists become very large. Drawings and Data Shortcuts cannot be filtered or grouped. Files are not sorted alphabetically, even though they follow a strict naming convention. Finding the correct drawing or shortcut becomes time-consuming. From our perspective, implementing alphabetical sorting would already significantly improve usability.   Questions for the Civil 3D/Vault team Could the team investigate whether any of the following would be possible? Allow introducing subfolders within the Vault C3DData folder while maintaining Data Shortcut functionality. Provide filtering or grouping options for drawings and Data Shortcuts in the Civil 3D Toolspace. Enable alphabetical sorting of the lists displayed in the Vault Projects section of the Civil 3D Toolspace. Suggest any alternative approach that would improve navigation and usability while preserving the current Program-level Data Shortcut structure. Show More