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.
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."
Can we please be a little more descriptive in the error messages?
I get a message that tells me I cannot move a specific file in the vault from one location to another.
The message reads "File Cannot be moved" looking at the details it says "File could not be moved due to vault error"
Really? Why couldn't it have explained to the detail of saying one of the factory files was checked out causing this file not to be moved. This is just one example. I would like to see all messages be a little more descriptive.
Side note. I would like to see less messages as well. That is more of how the software is written though.
We are trying to add a stamp or Water mark in the file preview based on life cycle state change. There should be a option in the API to do so, based on the requirement in life cycle state change. Even tried to check if any event is assosiated with preview tab click.
The Lifecycle Event Editor is currently available only through the Vault SDK. However the tool is not just for custom programmers. For example, it's used to configure Project Sync. Making it part of the Vault client would make admin tasks more convenient.
My understanding is that Vault currently uses a client local version of MS Reporting Services to render reports in the Vault client. I would like to see support for the server version of Reporting services. This way I could write companywide dashboard reports. I would also be able to link Vault data to ERP system data. We should have a way to use Vault API calls when developing SSRS reports. If there is currently a way to do this I would like to know.
When it is being sold as the integration point for Vault, the Item Master is inadequate.
First, lifecycles for items should be as configurable as for files. If you use the system as intended and control the lifecycle of the file through the item, you are severely constricted.
Items should assume the properties of the files that created them, or they should be easily called through the API.
Given the possibility that an item could be created before the CAD representation exists, there needs to be an ability to attach a CAD file as a representation of an item after the item has been created (this is also a huge hurdle if a company converts a product from 2D to 3D).
Document item types should exist so that external applications can reference and control files that don't represent parts.
OR do away with the item master and integrate the BOM capabilities (for 2D and 3D) of item master into the file interface and do away with item master altogether.
This would probably help with any plm integration, PLM360 included.