For Vault Numbering Scheme Skip button Lock option from vault. as if we have  this skip option in that case users are skip this and crate number what they want. in vault we should have option do you want this skip button yes/no. so that admin can decide base on the requirement.    Show More

Many companies use Autodesk Vault Professional as the central system to manage engineering workflows through Lifecycle States. While Vault stores the current lifecycle state and historical versions, it does not expose the date/time when a file entered each lifecycle state as a reportable property. This makes it impossible to create dashboards and KPIs such as: Time from Project to Design Time from Design to Engineering Validation Time awaiting Engineering Approval Time from Engineering Approval to Release Overall engineering lead time Average approval time by user or department Engineering workflow bottlenecks Today, the only available date is the Check-In Date, which is not the same as the Lifecycle Transition Date. Having access to lifecycle transition timestamps would enable powerful reporting without requiring SQL queries, custom jobs or external databases. Suggested implementation Expose lifecycle transition information through Vault properties and Report Templates, for example: Current State Entered On Previous State Previous State Date Lifecycle Transition Date Lifecycle Transition User Even better would be exposing the complete lifecycle history as reportable data. This would greatly improve reporting, dashboards and engineering KPI monitoring while keeping Vault as the single source of truth. 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

If you try to change an Item Number, and alter the Case of the Item Number (Vault 2023) nothing happens. The Item Number remains in the case it previously was. Where Item numbers are imported from CAD, and an error exist in the CAD, it may not be possible to correct the numbering. Whilst vault may be case insensitive down stream ERP systems may be case sensitive. Ideally Vault would allow corrections to case. Show More

In Inventor 2026, when using Save As with Vault Data Standard enabled, both the original document and the newly saved document remain open.   The expected behavior of Save As is for the newly saved document to become the active document and for the original document to close. This is also how Save As behaves in Inventor 2026 when Vault Data Standard is not enabled.   Please add an option for Vault Data Standard to automatically close the original document after a successful Save As, leaving only the newly saved document open.   This could be the default behavior or a configurable Vault Data Standard setting.   Related Autodesk Support case: 26093373 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

Measuring distance between cylinders and other objects is extremely difficult. Experienced CAD users are able to get accurate dimensions with sections views and snaps but less experienced users like fabricators cannot measure distances with confidence.   Image attached shows Thin Client Viewer VS Solidworks eDrawings.   Idea: When measuring a cylinder in Thin Client Viewer, use the center axis of the cylinder as the measure point rather than an exterior surface. Show More

When viewing an IDW via Thin Client Viewer, if a user chooses an annotation first(center mark, center line, dim extension line, etc) the only available entities to measure to are other annotations. Measuring between annotations returns a paper space dimension or the physical distance on paper, not the model dimension. Calibrating the measure tool does not help, as this also recalibrates the model entities.   Idea: Have the paper space annotations pull model distances by default.  Show More

Currently, Autodesk Vault allows users to move released files within the Vault folder structure or rename folders that contain released files. While these operations are technically possible, users are often unaware that such actions may have downstream impacts on linked data, references, Inventor models, drawings, or automated processes such as iLogic rules.   https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Downloading-a-drawing-from-Vault-triggers-Before-Save-iLogic-rules-in-Inventor.html   Because the consequences are not always obvious, users may unintentionally trigger changes that affect released data, resulting in additional validation efforts and unexpected behavior.   Introduce a configurable warning or information dialog that is displayed before performing actions that affect released files, including: Moving released files to another Vault folder Renaming folders that contain released files Other operations that modify the location or references of released files The notification should clearly explain that the selected action may have consequences for associated files, references, and automated workflows. Optionally, administrators could be given the ability to enable/disable this warning and customize the message.   Example:  Warning: The selected operation affects released files. Moving files or renaming folders may update references, trigger automated processes (such as iLogic rules), or impact downstream workflows and integrations. Please review the potential consequences before proceeding. Do you want to continue?   An engineer attempts to move a folder containing released files or rename a folder in Vault. Before the operation is executed, Vault detects that released data is affected and presents a warning message explaining the possible consequences. The user can then make an informed decision to proceed or cancel the operation. Show More

Currently, the State Glyph functionality allows colored icons to be displayed in the Where Used tab for files and in the Bill of Materials tab for items. We would like to request a more flexible and efficient conditional row formatting capability for grid views. Ideally, administrators should be able to define custom formatting rules based on property values and lifecycle states. For example: Display the entire row text in red when the item or file state is Obsolete. Display the entire row text in light red when the state is Work in Progress and a specified custom property contains a value. Display the row using the default black text when no defined conditions are met. Such a feature would significantly improve visual identification and usability when working with large datasets, allowing users to quickly recognize important conditions without relying solely on state glyph icons. Show More

When running validation on a Vault; Create a log file of *all* files that fail validation. Not just the files that failed the most recent validation. Include the file name (as shown in Client), the MasterID, the Version and the file name and path in the filestore. Allow validation to run while the Vault is live, i.e. don't stop the Vault while validation is in progress. Currently validation only logs new errors in the ADMS Filestore Logs. This takes a lot of work to parse these logs and extract the above information. Plus, the MasterID isn't reported so the records are hard to find in the database. Only files which have failed since the last validation seem to be reported, so it's impossible to even attempt to fix a file that failed previously. So the log needs to include *all* files that fail validation. It would be very helpful if validation could be run without stopping access to the Vault. We don't have enough downtime between the end of one working week and the start of the next, to run validation on live data. The only time I can run it is on a backup, after I have created the backup. 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

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

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

The current Rename Wizard in Autodesk Vault is functional, but quite limited in everyday use. To significantly improve usability and efficiency, I would like to propose the following enhancements: 1. Non-blocking Search & Replace Window Currently, the “Search & Replace” window blocks the Rename Wizard and the Vault main window. Problem: No simultaneous access to Vault data during renaming Texts or file names cannot be easily copied and reused Re-running searches or comparing names is cumbersome Suggestion: The Search & Replace window should be non-modal (non-blocking) Allow users to work in parallel by: Navigating within Vault Copying file names or text Flexibly building and adjusting search/replace patterns This would significantly speed up workflows and make the process much more intuitive. 2. Extended Rename Functionality (similar to “Joe Rename”) The current Rename Wizard only offers very basic functionality. Problem: Complex renaming tasks require multiple passes No support for combining rules No dynamic elements (time, counters, etc.) Suggestion: Introduce an advanced, rule-based renaming system with combinable functions, such as: Combinable Operations Search & Replace (existing but should be expanded) Add prefix / suffix Remove or extract substrings Change case (upper/lowercase) Dynamic Elements Insert date/time (e.g., YYYY-MM-DD) Automatic counters (incremental numbering) Custom placeholders Multi-step Processing Multiple rules applied sequentially Full preview before execution Preview & Validation Live preview of new file names Collision detection (duplicate names) Warnings for invalid characters Benefits of These Improvements Significantly more efficient batch renaming Reduced risk of errors through better preview features Less need for external tools A more modern and flexible user experience Conclusion: By introducing a non-blocking UI and a more powerful, rule-based renaming system, Autodesk Vault could greatly improve usability and productivity—especially for power users and environments with large datasets. Show More

If the options "force unique file names" and "allow duplicate file names for..." (with specific file extensions and folders selected) are enabled, all duplicate file names are still displayed, even though they should be excluded by the filters. => see attached screenshot Yes, it is known that one can use the print preview and export to XLS to apply a filter there, but end-users criticize this behavior; from their perspective, the display is incorrect or erroneous. Administrators would like users to see a filtered list of duplicate file names immediately, as there is always an underlying concern that the applied filters are not working. We request that the applied filters be integrated as a toggle option, or that the configured filters be applied to the displayed list by default. => see supportcase 26040459     Show More

When the Job Processor creates a design representation (e.g. DWF, PDF, or other derivative outputs) from a source file, the check-in or state change comment of that source file is currently lost. The generated representation either has no comment or only a generic, job-generated entry. It would be very helpful if the comment entered during the check-in of the source file were automatically transferred to the newly created representation file — for all target file variants (DWF, PDF, and any other output format produced by the job). This would preserve the context and intent that the author documented at check-in (e.g. revision notes, change reasons) right where it is most useful, without requiring a manual second step.   Preferred behavior: when a design representation is generated by the Job Processor, the check-in comment of the source file should be copied into the comment field of the created representation file. This should apply consistently across every target file type, so the original context travels with the derivative regardless of output format. Show More

It would be great to have the option of requiring a comment upon check-in of a specific file type.  For example, if I keep building files in Vault, it would be great to have the ability that if the file is checked out, before it can be checked back in, a comment has to be added describing what was done to the file.  Even though you have the ability to require a comment upon lifecycle changes, I feel it would just discourage people from changing the lifecycle state.  This will help encourage accountability for files that are utilized as an x-ref. Show More

Since iLogic is now better integrated with Vault Pro, it would be important to enhance the "Place iLogic Component to Place iLogic Component from Vault" tool in Inventor. The current tool places iLogic assemblies with uncontrolled numbering, adding suffixes such as -01, -02, etc. In addition, only the top assemblies are renamed this way. If any of the component parts also need to be modified, this becomes problematic. Therefore, this new tool should automatically launch an internal iLogic rule that would manage a Copy Design process, providing control over file naming as well as the reuse or copying of files, including associated drawings. This enhancement would finally make it possible to use iLogic Component Placement while maintaining full control over naming conventions, file reuse, and the copying of child files, including drawings. Show More