When we create a plant layout in Inventor (or any other large assembly) we often struggle to check that new top-level assembly into Vault due to it having what Inventor sees as an unsaved change or “dirty” file. This caries on after the initial check in with every subsequent check in making it very frustrating to check it in later. Most of the time the files that Inventor sees as "dirty" are because they are sub-assemblies with flexible positional representations, these assemblies are also in a released state so we couldn't check them out to save them anyway.   This causes our team working with very large layouts a lot of headaches. Most of the time that team will only have the very top-level assembly checked out as that is the only file that they need to edit. For initial check in we have been forced to check in an empty assembly with the name we want and then saving over the top of that so we can fool Vault to let us check it in. For subsequent check-ins we have been getting around this partially by either saving the files out of turn or saving only the top level that is checked out and then closing the assembly so we get the prompt to check in on close. This works most of the time (80%) but when it takes up to 30 minutes to open an assembly to just close it again to check it in, we lose large amounts of productive time! This also doesn't work if you have other assemblies open and just want to update the layout in the Vault.   We need a way of being able to check in just that assembly regardless of the state that Inventor thinks its children are in. If all the child files are the latest version in the Vault I can’t see why this isn’t possible. Show More

Replace the old search index system with a more modern search technology based on SQL technologies.   The search index system in ADMS has been a feature since the early Vault. The system now seems outdated and no longer really meets the criteria of speed and reliability expected of software like Autodesk Vault.   Articles like this one : Help - Rebuild Search Indexes  or this one : Using Wildcards take too long  should be a thing of the past. Show More

Hello.   It would be great to have a detail enhancement on "Can't change state" error / restriction dialog. Currently users get the message that "something" is wrong, but have no idea what to check and fix.       Best regards, Rene Repina Show More

Hello, This is a small idea but this might help the administrator and users.   Would it be possible to add an new attribute "COMMENT" to let the administrators to describe the attribute. moreover if this comment might be displayed in a kind of tooltip/infotip to help the user to know what the attribute represents.   Best regards Show More

Currently, the PowerShell scripts and modules in the Data Standard are frequently reloaded by the system—sometimes even twice for each action. For example, before every command execution via Data Standard (e.g., editing a file datasheet), all PowerShell scripts are reloaded twice. During the development phase, this is convenient because the application doesn't need to be restarted after modifying the scripts. However, in later stages of operation, this becomes unnecessary. Especially in more complex environments, loading the scripts and modules can take a considerable amount of time, significantly slowing down performance. Over the course of a workday, these PowerShell scripts are reloaded very frequently.   I believe it would be beneficial to make this behavior configurable. This way, we can retain the current behavior during development but avoid redundant script loading in regular operation Show More

There should be a way to retrieve different revision levels of an item in an item BOM, similar to model revisions in Inventor's Vault tree.           Show More

Would like to see batch/multiple file print as an option in the Thin Client Show More

When renaming multiple parts in Vault it is cumbersome and sometimes people forget to also show hidden files and rename the .dwf files for each corresponding .ipt   Is it possible to include these files in the rename so that you don't need to rename things twice? Show More

Since Vault 2024.2 admins can distribute (Custom) Views to all the users on the Vault. So far, the feature is really appreciated but only missing one more feature that would might enhance it even further.   It would be great to be able to select and set a (Distributed) Custom View as a Default View per user for the every folder. As an administrator of the Vault, I've made several distributed views for different departments. Not all departments use or need to fill in all the data in the Vault. The users will only see what they have to fill in or is useful to them.    Currently, this can only be done by selecting one folder and set it to the preferred custom view. This is a tedious process and many users wouldn't bother.   Show More

Die Teilenummer ist das zentrale Erkennungsmerkmal im Vault. Gibt es eine Möglichkeit die Teil-/Artikelnummer im Plotmanager einzublenden? Wir müssen häufig, wenn wir die Zeichnungen plotten, dann nach Nummern sortiert drucken. Der Dateiname ist unpassend, da ein Artikel mehrere Zeichnungen und damit unterschiedliche Dateinamen haben kann. ------------------------------- The part number is the central identification feature in the Vault. Is there a way to show the part/article number in the plot manager? When we plot the drawings, we often have to print them sorted by number. The file name is inappropriate as an article can have several drawings and therefore different file names. Show More

Vault copy design is an important function for companies increasingly committed to modular design and reuse of standard manufacturing parts. Copy design is an important function in this. With copy design, the engineer chooses which parts to reuse and which parts to copy. What often goes wrong is that the engineer unconsciously makes copies of parts that should actually be reused because they are standard components. Request for improvement; can Vault Copy Design be given a Configuration Rule in which it can be preset which file categories are reused by default and which categories are copied by default? That way the engineer gets a recommendation that can be adopted. This prevents uncontrolled copying of std parts.   See Image for suggested idea. Thanks  Martijn van Giels Arkance  Show More

Hello, In our drawings we have installed the machine frame as a "reference" assembly for better understanding. We use the model states for this. 1. Model state = standard, Machine frame is suppressed and set as a parts list reference 2. Model state = ZNG, Machine frame is not suppressed and set as a parts list reference   Problem with release: We release subassemblies (example: hydraulics + tank) beforehand, even though the machine frame is still being designed. However, this is not possible with an evaluation of the frame, as I have to set all installed models to the "Released" state when the hydraulics are released. The frame would unnecessarily increase the revisions in the prototype phase. It would make sense to expand the "Control" status when changing status. There are currently the "Control" status for "Released" and "Obsolete". Another could be added here for BOM- Reference that should not be taken into account when changing status. As the references are also evaluated when the article is created, you should be able to access this property. --------------------------------------------------------------------------------- Hallo, In unseren Zeichnungen haben wir zum besseren Verständnis den Maschinenrahmen als "Referenz"- Baugruppe verbaut. Wir nutzen dafür die Modellzustände. 1. Modellzustand = Standard, Maschinenrahmen ist unterdrückt und als Stücklisten- Referenz eingestellt 2. Modellzustand = ZNG, Maschinenrahmen ist nicht unterdrückt und als Stücklisten- Referenz eingestellt Problem bei der Freigabe: Bei uns werden Unterbaugruppen (Beispiel: Hydraulik + Tank) vorher freigegeben, obwohl am Maschinenrahmen weiter konstruiert wird. Das ist aber mit einer Auswertung des Rahmen nicht möglich, da ich bei Freigabe der Hydraulik alle verbauten Modelle in den Zustand "Freigegeben" versetzen muss. Der Rahmen würde in der Prototypen Phase die Revisionen unnötig nach oben treiben. Es wäre sinnvoll, den "Control" Status beim Status zu erweitern. Es existieren derzeit die "Control" Staten für "Released" und "Obsolete". Hier könnte eine weitere hinzugefügt werden für Referenzen, die nicht berücksichtigt werden sollen. Da die Referenzen auch bei der Artikel- Anlage ausgewertet werden, sollte man auf diese Eigenschaft zugreifen können.        Show More

Users would like better support for file handling within the autoloader. It's great that the autoloader detects errors, but why can't you replace or search for the faulty files? If, for example, data is missing that is located on an inaccessible external drive, why is there no way to change the path in the autoloader?       Show More

I thought there was an idea for this, but I am unable to find it today - I know Autodesk is aware of it.   It would be great if we could edit the properties of files in the copy design window while doing a copy design. We can view them there - but we are unable to edit. Show More

User wants a support to DataStandard for all integrated Autodesk Applications. For Customers is it not ease of use to have different workingpath for file handling and properties in the files. Please integrate all Autodesk Applications at Data Standard. Show More

Please add the ability to use user/system properties in Vault's numbering schemes Show More

Vault Professional with AI with API - Integration Allow to questions the overall status of a product development on a short Office or PowerPoint as examples. AI should collect Vault information's on latest design phase and approved documents. example: Created me a summary page on Product ABC including text pictures, based on available documents stored in Vault (Product claim general drawings, 3D views, test reports, files states; Evaluated how many working hours has been pend on Project ABC in Vault based on check in check out, release workflows spent..   Result should only fit User access rights if no access no answers. Add specific users to have the right to use Vault AI (role based users). Show More

Scenario: Beside the zero migration strategy, there are situations where all Inventor files need to be migrated.   Current challenges:  Task Scheduler allows only to select folders. There is no indication if files in such folders are already migrated or not. Task scheduler can skip already migrated files but will need to check out and handle them anyways. Number of files handled in one Task is set by the number of files in a folder. For big folders this could result in Tasks that run for days. Reused files are "touched" multiple times. When migrating assemblies or drawings with its children, due to heavy reuse (content center for example), it could be that base files get checked out, checked and checked in hundreds of times over the course of the whole migration. The later you are in the whole migration, the higher the percentage of already migrated files will be. There is no way to exclude already migrated files from being handled completely. Enhancement: If Task Scheduler could access Saved Searches, it would be easy to find non-migrated files (Comment/Application Version), define the number of files being handled in one task and reduce repeated handling of reused components to a minimum.   Result: Massive reduction in overall time for migrating all Inventor files.   Show More

I was initially trying to create a search criteria to search the Part number field for the quotation mark character. That wasn't working, for obvious reasons. @ihayesjr had helped me, by making me aware of the Column Filter. That will be useful, as I can set the filter, and quickly apply it to folders, but this is a one-by-one process. Can the Column Filter be made to apply itself to a folder, and include its subfolders, or the Vault as a whole? Show More