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

Problem Currently, it is possible to visualize CAD files in Vault Thin Client and Inventor View, but there is no way to select or switch between Design View Representations created in Autodesk Inventor assemblies. This limitation makes it difficult to review assemblies that rely on Design View Representations for: Manufacturing sequences Assembly instructions Maintenance procedures Spare parts identification Alternative product configurations Simplified visualization of complex assemblies While Design View Representations are fully available inside Inventor, users reviewing data through Vault Thin Client or Inventor View can only see the default representation. Proposed Enhancement Allow users to: View the list of available Design View Representations stored in an assembly. Switch between Design View Representations directly in Vault Thin Client. Switch between Design View Representations in Inventor View. Preserve visibility states, section views, appearance overrides, and camera positions associated with each representation. Benefits Better collaboration between engineering, manufacturing, purchasing, quality, and service teams. Improved support for assembly instructions and spare parts documentation. Faster navigation of large and complex assemblies. Greater value from Design View Representations already created by engineering teams. Today, an assembly operator may open Vault Thin Client and be unable to select representations such as SPARE_PARTS, ASSEMBLY_SEQUENCE, HYDRAULICS, or other Design View Representations, even though they already exist in the Inventor model. As a result, much of the value of these representations is lost outside the Inventor environment. With the growing adoption of Model States and digital manufacturing workflows, Design View Representations have become increasingly important for communicating assembly, service, manufacturing, and spare parts information. Making them available in Vault Thin Client and Inventor View would significantly improve collaboration and accessibility across the organization. As a CAD administrator and advocate for Autodesk solutions, it can sometimes be frustrating to promote the value of Autodesk Inventor Professional and Vault Professional to manufacturing, assembly, quality, purchasing, and service teams, only to encounter workflow limitations such as this one. One of the key strengths of the Autodesk ecosystem is the ability to provide access to engineering information beyond traditional CAD users through tools such as Vault Thin Client and Inventor View. However, when users on the shop floor cannot access existing Design View Representations such as SPARE_PARTS, ASSEMBLY_SEQUENCE, HYDRAULICS, or other purpose-built views, an important part of the engineering intent remains locked inside Inventor. This may appear to be a small enhancement, but it would significantly increase the practical value of Design View Representations and further strengthen Vault Professional as a collaboration platform across the entire organization. Show More

When exchanging design-related, project-specific documents between two Vaults, Fusion Team Hub (FTH) can serve as the intermediary platform. The upload from Vault A is initiated by selecting the top-level assembly and synchronizing it to FTH via Dekstop Connector. However, if one subsequently wishes to download this assembly into a different Vault—Vault B—the process works only selectively, as the synchronization currently imposes a limit of no more than 50 documents at a time. If the assembly contains 5,000 components, the user is forced to initiate the download 100 separate times. This is an extremely time-consuming and frustrating experience for the user! Please lift the document quantity limit for downloads! Furthermore, provide the option to initiate synchronization—for both uploads and downloads—on a folder-by-folder basis. Doing so would significantly boost user adoption and acceptance of the FTH platform!   Möchten man konstruktive, projektrelevante Dokumente zwischen zwei Tresor austauschen kann hierbei Fusion Team Hub (FTH) als Plattform genutzt werden. Der Upload von Vault A erfolgt, in dem die oberste Baugruppe selektiert wird und nach FTH via Dekstop Connector synchronisiert wird. Möchte man nun die Baugruppe in einen Vault B downloaden, funktioniert das nur selektiv da die Synchronisation nicht mehr als 50 Dokumente auf einmal zulässt. Wenn die Baugruppe 5000 Komponenten enthält, muss der Anwender 100 mal den download starten. Das ist sehr aufwändig und frustrierend für den Anwender! Heben Sie die Limitierung der Anzahl der Dokumente beim Download auf! Geben Sie die Möglichkeit auch ordnerweise die Synchronisation zum Up- und Download anzustarten. Das würde die Akzeptanz für die FTH Plattform deutlich erhöhen! 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

Dear Autodesk, When additional links are added to an item in Vault Professional, the corresponding files are successfully synchronized to Fusion Manage. However, when a link is removed, it is not automatically deleted in Fusion Manage and requires manual intervention. As we also synchronize data and files with SAP, maintaining an accurate and consistent file count is essential. Therefore, automatic removal of unlinked files is a key requirement for us in the Vault Connector to Fusion Manage. Thank you. Show More

Dear Autodesk, Within the Vault Connector settings for attachments, it should be possible to define a list of file types to be excluded from synchronization to Fusion Manage.     In our case we have also attached other file types which are not mandatory to be synchronized to Fusion Manage.   Thank you 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

Dear Autodesk,   If you do a Copy Design to copy a CAD structure, the new files are not published with DWFs. It would be nice to have an option to enable it similar it is possible with check in operation from Inventor/AutoCAD Mechanical, so that the job processor is creating it in background.   Reason is, it is recommended to check out the new file structure to have ready the BOM blob for correct item/BoM assignment, but if not everything (specially IPTs and IDWs) is checked out/in, DWFs are missing. Sync items to Fusion Manage would be happy to receive always the DWFs.   Thank you 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

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 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

Dear Autodesk,   When synchronizing an item in Vault Professional that includes an linked IDW or DWG file as a attachment, the corresponding DWF visualization is not transferred to Fusion Manage. As a workaround, the DWF file must be attached to the item manually; however, this approach does not meet our requirements.   Users consistently attach native Inventor and AutoCAD Mechanical files. Therefore, the Vault Connector is expected to automatically include and synchronize the associated DWF file with Fusion Manage.   Thank you Show More

Problem A very common requirement in Vault is to automatically populate revision and approval fields on drawings based on lifecycle state changes (Designer, Checker, Approver, Approval Date, Reason for Issue, etc.). Today, this typically requires: Third‑party Vault extensions, or Custom jobs built on top of the Job Processor The end goal for most users is simple: clean, correct data that can be shown directly in the drawing revision block.   Proposed solution – Property mapping on state change Introduce a built‑in Property Mapping on Lifecycle State Change feature. On each lifecycle transition, administrators can define one or more mapping rules: Source: system property, user‑defined property, or static text Target: any writable property Action: copy value, set static value, or clear value The mappings are executed automatically on state change, using the existing Job Processor. This provides a generic and flexible automation mechanism for setting, transferring, or clearing properties based on lifecycle transitions, without custom API code or third‑party extensions.   Example workflow Typical use cases include populating revision tables, drawing signatures, approval initials, and approval dates based on lifecycle state changes. Work in Progress → For Review Copy Created By → Designer For Review → For Approval Copy Created By → Checked By For Approval → Released Copy Created By → Eng. Approved By Copy Created Date → Eng. Approved Date Set Reason for Issue = "Issued for Construction" Released → Work in Progress Clear approval and revision‑related properties These properties can then be referenced directly in the drawing revision block, which is the primary driver for this feature.   Value Clean, automatic revision and approval data without custom jobs or extensions A reusable automation mechanism for lifecycle-driven metadata Show More

For example, if a job processor machine has trouble obtaining a license, it currently “kills” all tasks in the scheduler for its fellow job processors. Preferred behavior: after, for example, 3 consecutive failed tasks of the same type, the affected job processor should stop processing further tasks. It would also be helpful to send an email notification to the administrator. Show More

I believe it would be extremely valuable to have a centralized visualization and management tool for security permissions across all files and folders within a Vault environment. Currently, understanding and managing permissions can be complex—especially for non-expert administrators. There is no native tool (to my knowledge) that provides a global, intuitive overview of permissions or helps identify inconsistencies with the overall security policy of the Vault. Such a tool should provide: A global and hierarchical view of permissions across the entire Vault (files and folders) The ability to easily identify non-compliant or inconsistent permissions compared to defined security policies A clear and graphical representation of inherited vs. explicit permissions Advanced filtering options (by user, group, role, folder, permission type, etc.) A way to quickly audit and troubleshoot access issues The plugin Effective Permissions Viewer available on the Autodesk App Store is a great starting point. It offers a visual and informative interface that makes permission analysis much easier and more accessible. However, it remains limited in scope and lacks native integration and advanced management capabilities. Building on this concept, a native Vault feature could go further by: Allowing bulk editing and deployment of permissions across multiple folders/files Simplifying the creation and assignment of new user groups Providing simulation tools (e.g., "what access would this user/group have?"? Offering policy enforcement mechanisms to automatically detect and correct deviations Enabling reporting/exporting capabilities for audits and compliance tracking This would significantly improve security management, reduce configuration errors, and save a considerable amount of time for administrators. Show More

Some customer says they would like to create items in Fusion Manage as a first step (i.e. for classification purpose or to create a skeleton of the BOM without any CAD in PLM) and after to align them in Vault. As of today Item Creation needs to be started in Vault, but it would be great to be able to perform also the vice-versa (creation of item in Fusion Manage --> alignment in Vault) Show More

When synchronising files in the Item editor, can vault auto update the file version to the latest (new created version).   Synching a File from an Item property change, and the having to update the Item Version as a 2nd Command seems an unnecessary step, that makes the user experience more painful than needs. Show More

We have do export our dwg as an eTransmitt out of AutoCAD at the end f our projects. This are may fils and exports. It wozld be grate, if there is a job of the job-processor that can do this automaticaly. It schuld be possible to config the settings for the eTransmitt. It have to be possible to define the settings specicicaly for diffrent projects, may be by using the category of the file. Show More

When I do a search in Vault sometime I get a result of hundreds or thousands files, I then have to keep hitting the More button I until Vault shows me all the files it found.   What I would love is a Show All button.  When I click on the this button, Vault will then display all the files it found.   I know that this can take some time for it to finish but it's better than me sitting there hit More over and over again. Show More