Navisworks if great for comparing a historical and current model. It is not possible to load historical revisions from models to compare them to each other. On this moment you need to models with different names/file type to compare them.
Not having this feature has a significant impact on the process for comparing models during design phase, particularly one which has a somewhat complex or large modeling projects.
Due to this product limitation, it might actually put users off from using Vault in combination with Navisworks.
Streamline the UI functionality between all Vault add-ins. The best example is AutoCAD with the ability to use shortcuts, saved searches from the dialog. And make it this way possible to use Revisions of a file to be loaded. By solving this the users know what to expect when opening files from Vault.
Currently you have to download a file to your local and then do to Design Assistant or open it in Inventor to see if the file needs to be migrated. I would like the option to be able to see if the file needs migrate and what version it was last migrated to. By having this option, I could easily see what needs migrated and what doesn't instead of hoping that I find them all. I know that someone could say 'just check out all the files and migrate them' but when your Vault has over 1.5 million files a growing it's not really an option.
Due to the huge impact of the purge operation on SQL and on replication performance in particular, would be useful to receive from the purge command and estimation about the number of files that will be purged and associated records to be replicated prior to the purge run. Also would like to have a more selective purge, for example by folder, in order to split the purge workload through different weeks.
All Vault properties are subject to rules such as "Requires Value" and "Minimum Length". If a property does not have a Value or meet the minimum length, a property non-compliance is raised and requires user input to rectify. This is really important for when a property must be completed for audit purposes and especially for exporting data into ERP systems.
ECO properties have these rules but they are completely ignored. I need to make sure users enter a value for these ECO properties but the only method in which I have to enforce this is not working, at all. Please fix ASAP.
From what I can tell right now, users have very limited control over the visibility of file records in the Thin Client. You can either see all versions of a document or all Released versions of a document. Both options can lead to confusion based on workflow.
What if you want to only show the latest Released version of a file record? You can't do that - all Released versions are currently displayed. Worse, what if you use a lifecycle like the built-in Flexible Release Process and perform a Quick Change? Now you have two versions at a particular revision. The result can be something like this:
To provide better control over file record visibility in the Thin Client, I'd like to see the options for File visibility expanded to a total of four (from the two we have now). These four options would be as follows:
Show all file versions
Show all Released file versions (allow multiple versions at the same Revision)
Show all Released file versions (show only the latest version of each Revision)
Show only the latest Released file version
I think one and four are self explanatory. Two and three might be confusing to the user, but I think they're ultimately necessary. Option two would function like the current 'show only released' versions, and would lead to a list like the screen capture above. Option three would be new functionality, and would hide all Released versions of a particular Revision level except for the latest. This option would hide versions that had been superseded by activities like Quick Change, and so in the example screen capture above, version 6 of the file would not be visible in the Thin Client.
We have an approval document that we attach to a drawing. That document only pertains to that one drawing. When using Copy Design on this drawing, however, it will keep the link to the approval document. This forces the user to go find the link and delete it. If they forget, it causes confusion. The same problem exists with properties, copy design does not offer an option to clear out properties when copying (as far as I know).
What we would like:
An option to strip attachments from files when copying a design.
An option to strip properties from files when copying a design.
Vault report templates use an older RDLC file format. Because of the older format, newer versions of Visual Studio cannot be used to edit these files.
The biggest advantage of the old RDLC format is that there are free editors available. I tested out Visual Stuido Express 2010 and 2012, and they do not support RDLC editing. I'm not sure if there are any free third-party editors for the new format.
Essentially, there's an option to enforce a value for ECO properties. But as confirmed by Autodesk, it isn't supported therefore it doesn't actually do anything even though the option is there, leading you to believe it should work:
My Idea is... if something doesn't work, isn't supported, can't function for whatever technical reason, remove the option from the product or grey it out.
I honestly don't mind if something isn't supported. I do mind wasting an hour or two scratching my head blowing time trying to make it work when all along the code behind the option just isn't there, it's disabled, it's wasted my time and annoyed me to boot.
This isn't restricted specifically to ECO properties, this applies to all other red herring empty duff options in Vault. The Item watermark 'transparent' colour option is one of a few I could back this up with!