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.
For files that may be stored in one folder, but may not be linked by a drawing, or top level assembly.
Provide a functionality (similar to Copy Design) to copy a folder. This would reduce the need to link files together, or create a "dummy" assembly to copy files related within a folder, but not connected directly by file heirarchy.
I see no reason for Vault to use numeric codes to represent errors. It would be much better if the error codes used words instead. For example, "InvalidUserPassword" is a much more useful error code than "301".
We would love to see the worklist color coded by state. Customizing the colors so we could pick what color was assigned to each state would be fantastic. But basically the idea would be to highlight each item in the worklist by state. So for example you red could be assigned to all change orders that have been approved and are needing effectivity to be set and closed.
I appologize for my coloring skills but here is what it might look like.
byJHUNT10707-30-201408:11 AM - edited 07-30-201408:14 AM
Please remove the "Details" button that expands the Warning/Error message windows. In my experience the average user doesn't even SEE the button. The button only hides relevant information from the user.
I'm curious what prompted the creation of the "Details" button in the first place?
Read only files or "non-checked out" files, continue to be prompted for saving inside of an Inventor assembly model. Why is this happening? I know the little messages (see Vault messages below) are supposed to let you know the file is not being saved back to Vault, but something is happening. Somehow the files become edited out of turn, which means they're being saved locally somehow. Then the Vault file and the workspace file are out of sync.
Can we just remove the Vaulted "read only" files from the assembly save dialog all together?
Is it possible to not change the local file in the certain way that makes Vault see it out of sync?
I have Vaulted released files that are part of assemblies that are checked out for editing and somehow the parts of the assembly that are not checked out seem to always become out of sync.
Also, some of these parts are iParts.
Please give this post Kudos if you have the "read only" file out of sync with Vault issue.
Autodesk: Please consider my request. Thanks.
"Write enable (not checked out from Vault)"
"'XXXXXX.iam' is currently locked. Do you want to continue editing anyway? Your changes will not get saved to the Vault."
When starting Vault Explorer (all flavours) 2013/2014/2015. the loading splash screen stays on top of everything while Vault loads. There is no way to hide it. This means you can't look at or do anything else in windows while you wait for the application to load. Where it is particularly frustrating, is when an error message pops up on loading and ends up hidden behind the splash screen. The only way you can continue, is to click on the message box in the task bar, and then use "Alt+Spacebar+M" and the arrow keys or mouse, to move the error dialog out from behind the splash screen.
I believe this is a regression. I'm sure that this behaviour was not present in earlier releases, but I could be wrong. More importantly, it is inconsistent with every other Autodesk product I have used. Usually, while the application is loading, you can click somewhere other than the splash screen, and it will hide it behind the active window.