When creating category rule in Vault to assing to Content center parts most people use the IS Content variable for the rule.  This variable is created for every part that comes out of content center and it is always set to TRUE.  The fact that it is always created is a blessing and a curse.  If you create a category rule alone using this variable all of your custom content center parts, or anything made with frame generator will be filed away under the Content Center category.   My suggestion would be to have Content Center create a seperate variable that matches the Standard or Custom options that are aviable to the Inventor user when making the part.  That way the Vault category rules will file the parts correctly.   This border lines Inventor request, but affects vault usage so feel free to move it if necessary. Show More

Some properties of the content center parts is very important but missing in Vault. For example:   the Standard property, the Size Designation property, and the IsCustomPart property.   All these properties are available in inventor (or in Inventor API) but not available in Vault. Show More

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

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