I'm not sure if this belongs here or in the Inventor idea Station, so feel free to move it if necessary.   When opening an assembly from Vault, through the Inventor interface, which includes Content Center parts that are in the Vault but not stored locally, Inventor & Vault know to look for those parts in the Vault and download them.  However, if the CC part was published from a derived part (since you cannot publish assemblies), Inventor also wants to have the base assembly that the part was derived from.  Neither Inventor or Vault is "smart" enough to know to look for that base assembly in the Vault, and so Inventor throws up a "Resolve Link" error on that assembly.  The only thing that can be done at this point is to manually locate the assembly in Vault client, and use Get/Checkout to download it to the working folder, and then manually resolve the link in Inventor.   What say you all? Show More

Hello,   Today to be able to modified files defined as a libraries in Vault we need to create special project file with allowe that modification.    It would be more logic and easier to set-up rights if those rights will be controlled from "Roles" perspective.    Thanks in advance.       Show More

When we get ready to upgrade to a new version of Inventor, the first thing we need to do is upgrade our Vault for testing purposes.  I am not ready to do the actual upgrade, but want a test environment.  There are other SQL based products that allow you to clone your production server and then go into SQL and update the tables to look at the new cloned server instead of the original server.  With the ADMS installation, I am told that this cannot be done.  So instead I have to have our IT department create a brand new server with SQL on it and then do a restore from our production server.  While that sounds easy to accomplish, it never seems to be in reality.  The first time they tried it, the IT department didn't get all of the correct SQL versions installed and although I was able to install the ADMS, when I tried to restore, it gave me an error saying they were not compatible.  After messing around with it for days, he finally started from scratch again and was able to get me something that worked but this entire process took me two weeks to get accomplished.  That is not acceptable.  With our other SQL product, it is accomplished in less than a day which includes them creating a clone of the server, and I manipulating the tables to no longer read the original server, but rather the new clone name. Show More

It would be helpful to be able to store sketch blocks on Vault for access by all users. This would also allow some file management of the sketch blocks. We use a lot of blocks in our business and at least 50% of them are project specific and will only be used for 1-2 years. The other 50% could go into a system folder for constant use. Show More

Currently VDS allows users to select/change file category for new files. It would be nice if change of category would be allowed at a later time if file already exist in the Vault. This is necessary when user brings/inserts file into vault rather then creates it from within vault.  Show More

The Thunderdome feature is a powerful tool that helps administrators efficiently deploy folders such as Libraries, Templates, Standard Components (e.g., iFeatures, Approved Content Center parts) to a user’s local drive upon first login. This capability is especially critical in environments running multiple versions of software (e.g., Inventor, Revit) to ensure users access the correct version-specific data. By integrating Thunderdome into the standard Autodesk Vault product, organizations can: ✅ Maintain consistency by ensuring all users receive the right deployment packages upon login. ✅ Enhance administration by keeping deployment packages centrally controlled and updated. ✅ Streamline multi-version environments by helping users get the correct libraries for their installed Vault and CAD versions. Proposed Enhancements to Thunderdome: Standard Feature Integration – Include Thunderdome as part of Autodesk Vault without requiring additional customization. User Control & Updates – Allow users to mute additional deployments but manually trigger them when needed. Automated Updates – Notify users when new packages are deployed by administrators to keep everyone aligned. Version Labeling & Compatibility Check – Clearly label deployments with the Vault and CAD software version they pertain to. If a user opens a deployment meant for a different Vault/CAD release, it should not prompt them to install it unnecessarily. Maintain support for three versions backward, aligning with standard Autodesk software versioning policies. Show More

We have in our vault libraries some home made standard components. Some of them are used directly as standard component like a Content Center part and a classic library part in read only, some others are copied with a copy design in the project to be parameterized. As the users don't read the procedures and don't follow the processes, we would like to be able to allow or forbidden the copy design on some folders or files with a security property or something like that Show More

An additional insert into cad function, but to replace the selected part/assembly in Inventor.   Show More

There is also a Property available in the "ContentCenter" Propertyset with called "IsCustomPart". For real Content Center Files placed as Standard the Value of IsCustomPart = 0 For real Content Center Files placed as Custom the Value of IsCustomPart = 1   This would help us a lot when this would be available to read/map in Vault too! Show More

Dokumente die noch keine Artikelverknüpfung haben lassen sich im Vault nicht ändern. Bei einer Artikelverknüpfung ist das ja erwünscht, aber Dokumente die nicht verknüpft sind können nur noch im Inventor geändert werden. Wird das Mapping dahingegen geändert das es möglich ist die Dokumente im Vault zu ändern. Entsteht wieder das Problem der unsauberen Synchronisation (leere Zeilen werden nicht übernommen). Die Idee war ja eigentlich Dokument die noch nicht verknüpft sind mit einem Artikel, können im Vault geändert werden. Ab einer Verknüpfung mit dem Artikel soll der Artikel führen seien. Ein weiteres Problem ist das Inhaltcenter. Die Dateien benutzen eine Exceltabelle um sich zu erstellen. Ist der Artikel führen ist es völlig egal was die Tabelle vorschreibt, es geht sowie so nicht. Ist erst einmal eine Abweichung entstanden, warum auch immer, kann der Benutzer nicht mehr mit dem Inhaltcenter arbeiten. Das soll heißen aus Inhaltcenter einfügen geht nicht mehr (außer der Nutzer hat Admin Rechte). Wie soll diese Probleme behoben werden. Zurzeit kann nicht mit einem Artikelgetriebenen Prozess gearbeitet werden, da es keine Lösung gibt wie mit Dokumente umgegangen wird die keinen Artikelverknüpfung haben und im Vault änderbar seien sollen.   Translation Article driven process Documents that have no article link cannot be changed in the Vault. For an article link that is desirable, but documents that are not linked can only be changed in the Inventor. If the mapping is changed because it is possible to change the documents in the vault. Again the problem of unclean synchronization arises (empty lines are not taken over). The idea was actually document that are not yet linked to an article, can be changed in the Vault. From a link with the article, the article should be lead. Another problem is the content center. The files use an Excel spreadsheet to create themselves. If the article leads, it does not matter what the table prescribes, it does not work either way. Once a deviation has occurred, for whatever reason, the user can no longer work with the content center. This means that inserting Content Center is no longer possible (unless the user has admin rights). How should these problems be solved? At the moment it is not possible to work with an article-driven process, as there is no solution how to deal with documents that have no article link and should be changeable in the vault. Show More