This is a follow-up to my related idea Make the Inventor "Fusion Exports" state visible in Vault. Even if you know that a file was uploaded to Fusion, there is currently no way to tell in Vault whether that upload still matches the current design.   Problem Inventor tracks this. When the model has changed since the last upload, the Fusion Exports node reports that "the Inventor model and Fusion export are out of sync", and the commands Upload new version and Update and Open only become available if changes were actually made (see Inventor Help: To Connect to Fusion Workspaces). Vault, which is the system that actually owns the version history, knows nothing about it. So the situation is inverted: Vault creates version 12 of the assembly, but only Inventor can tell me that Fusion is still working with the data from version 8. As a Vault user – and especially as a project lead or reviewer who does not open every model in Inventor – I have no way to see that the cloud copy is stale.   Request Compare the Vault version the Fusion export was created from against the current Vault version of the file, and surface the result in the Vault Client: a file property such as "Fusion Export Status" with values like Up to date / Out of date / No export store and display the source version, e.g. "Fusion Export based on Version", next to the current version an icon or column in the file list, plus the detail in the file properties pane usable in saved searches, so I can list every design whose Fusion export is outdated optionally: trigger this as part of the existing Collaborate / Upload to Cloud Drive workflow, so an outdated export can be refreshed directly from Vault instead of having to open Inventor   Benefit Prevents simulation, generative design or CAM work in Fusion from running on an obsolete geometry state – a real and expensive risk today Puts the sync information where the version data actually lives, in the PDM system Reviewable across the whole vault instead of file by file Removes the need to open every model in Inventor just to check the Fusion status Closes the loop with the Vault-side upload command, which currently offers no feedback at all   Background Raised with Autodesk Support under case number 26300750. Support confirmed there is no such functionality in Vault today and suggested submitting it here for the Vault team. Show More

When an Inventor part or assembly is sent to Fusion – either from Inventor (Fusion tab → Upload) or from the Vault Client (Collaborate → Configure → Upload to Cloud Drive) – Inventor records this in the model: a Fusion Exports folder with a linked node is added to the model browser (see Inventor Help: To Connect to Fusion Workspaces). Inside Inventor this is obvious. Inside Vault it is completely invisible.   Problem As a Vault user I cannot tell whether a file has already been uploaded to Fusion. There is no property, no icon and no column that exposes this. To find out, I have to open the model in Inventor and look at the browser, or go to the Fusion web client and compare by hand. In a vault with thousands of files that does not scale, and it makes governance of cloud-published data essentially guesswork.   Request Expose the existence of a Fusion export as file information in Vault, in the same spirit as the existing indicator for Inventor Model States ("Contains Model States"): a file property such as "Contains Fusion Export" (Yes/No), indexable and usable in columns, saved searches and lifecycle criteria ideally the export details as well: export/node name, target Fusion project/folder, upload date, and a link to the Fusion web client item an icon or column in the file list, and the information in the file details pane   Benefit Instant answer to "has this design already been shared to Fusion?" – without opening Inventor Traceability and compliance for data published to the cloud, directly in the PDM system Saved searches / reports on all designs with a Fusion export Consistent behaviour: Vault already surfaces other Inventor-internal states (Model States, drawing existence), so this closes an obvious gap Makes the Vault-side "Upload to Cloud Drive" workflow actually reviewable   Background This was raised with Autodesk Support under case number 26300750. Support confirmed that no such indicator exists today and recommended posting it here as an idea for the Vault team. 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

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

Many organizations are required to keep Microsoft SQL Server patched to meet security and compliance obligations. However, Autodesk will only support the CU build that was tested when developing that version of Vault. See: Vault support for Microsoft SQL Server Cumulative Updates   This leaves customers having to choose between remaining on older SQL Server builds that are supported by Autodesk, or applying newer Microsoft security updates that address critical vulnerabilities but have not yet been confirmed as supported for Vault.   Requested Improvement: Autodesk should update the supported SQL Server cumulative update guidance for Vault more frequently, particularly when Microsoft releases security updates that address known vulnerabilities. Customers need to be able to remain compliant with internal security policies while continuing to operate within Autodesk-supported configurations. 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

Autodesk Access currently allows users to install Autodesk Vault Server updates directly from the Autodesk Access interface. In practice, Vault Server updates often require administrator oversight and preparation, including stopping dependent services such as IIS, Job Dispatch, etc. Installing updates through Autodesk Access bypasses this intentional process and can lead to failed or incomplete updates. A few cases have been observed where Vault Server updates initiated through Autodesk Access become stuck during installation (for example, Vault 2025.4.2 hanging at 97%), leaving administrators with no option but to terminate the installation through Task Manager. Suggested Improvement: Exclude Autodesk Vault Server updates from Autodesk Access and require server updates to be installed using the standalone installer. Alternatively, if Vault Server updates remain available through Autodesk Access, provide clear warnings and validation checks to ensure that all required services are stopped before installation begins. 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

Vault's Fusion Manage Panel allows to initially release a component's item without switching applications. That's a great enhancement of Vault 2027 Update 1. However, once the related FM item is released, we can no longer create Change Orders/Requests/... for a component, due to a missing switch/activation of the latest working revision. It affects not only this workflow. Any new Vault to Fusion synchronization applies to the working revision and can't be monitored as our view is static for the latest production release. 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

The Affected Items tab in the Vault Fusion Manage Panel currently does not provide the same functionality as the Affected Items tab in Fusion Manage. The following capabilities are missing today: Edit affected items and define a target State There is currently no option to edit an affected item and assign its target State. This is the most critical gap, as it can prevent the user from progressing the Change Order entirely from within Vault. To continue, the user has to open the Change Order in the browser version of Fusion Manage, set the Target State there, and then return to Vault. Bulk Lifecycle Changes Fusion Manage provides the ability to update the Target State for multiple affected items at once. This bulk action is currently missing from the Vault panel. Adding it would significantly improve the experience for Change Orders containing many affected items. Add related items to the Change Order The Vault panel is also missing the ability to add related items, such as the children of an affected assembly, that also need to be included in the same Change Order. This functionality would make it much easier to build the complete list of affected items without switching to Fusion Manage.  The first point is a workflow blocker, while the other two are significant quality-of-life improvements that would bring the Vault experience much closer to the existing Fusion Manage workflow. A possible workaround for the first two points is to configure a workflow transition that automatically assigns a predefined Target State to the affected items. However, this removes flexibility from the user and is not an ideal substitute for being able to manage the Target State directly from the Affected Items tab. The attached video shows these missing capabilities and the difference between the current Vault Fusion Manage Panel and the Affected Items experience available directly in Fusion Manage.             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

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

Distributed views should also be made available for the CopyDesign dialogs 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

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

Vaults Rename Wizard shoudl have a button for Find and Replace like the one in Copy Design. This would build consistency within the same program. I had no idea Rename Wizard even had a find replace until today and I've been in vault for 15yrs.      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