When I am changing my frame using the frame creator it keeps giving me this error message.
Now I am thinking this error message that keeps poping up everytime I either go to add a frame piecve or delete a frame piece speaks to why I just lost all of the frame assembly I created this morning and was checked into the vault, but when it was checked out was right back to where I started from.
Can someone please give me a resolution to why this error message keeps popping up?
Could you please let us know the exact workflow (May be a video?) that you are using along with the versions of Inventor and Vault?
That would help us to understand the issue better and also we can try the same here.
Thank you for your response.
I am running 2012 with Inventor as well as vault.
As far as the sequence goes. I had my frame checked out of the vault.
I needed to make modifications which required adding as well as deleting some frame members.
In this process is when I ket getting this error message. The first time I I was making these modificatins when I was done I checked the assembly into the vault. When I called up my top level I noticed that the changes did not stick.
I have since gotten this updated and I am not seeing this message nearly as much. Nit sure what changed, but I would like to know for future reference.
Thanks for your reply.
The message indicates that the local file is not matching with the one in the Vault. That's the reason you are asked to get the latest from the vault before you do the edit.
If you open the file from Vault before editing then you will not see this message.
Hope that clarifies.
Thank you Senthil.
Yes that makes sense. I am try to get used to this. That might seem like a strange statement, but from where I am coming from being used to Solidworks PDM workgroup, when you have something checked out and it remains checked out there is not this constant back and forth. Infact you can close it out of session from one day to the next and call it up from the local and it remains checked out without an issue and still check it in. With vault it seems even if you keep it checked out you constantly have to call up the file from the vault if it is closed in your session.
Is there a setting that could similate more of what I am used to with the SW PDMW?
Actually Vault also works the same way with the workflow you mentioned. If you have checked out the file, it remains checked out to you till you check it in. Do let me know if you see it otherwise. May be you have to give me the steps so that I can understand the workflow that you do.
One thing you need to know is if you are working on an assembly and you have only checked out the assembly and not the Parts, and then the parts are checked out, modified and checked in by someone else, then the local file (Part) that you have is out of date from the Vault. In that case you have to get the latest version from Vault if you need to consume that part for the assembly.
Hope this helps.
Thank you Senthil,
What you said makes sense and I have experienced that. We just went live with vault about 6 weeks ago so I know this is a process. I have just experienced times where I know I have checked something out and yet it will ask me again when I open up an upper level assembly and it will ask me yet again. I will continue to monitor this (more closely) and keep you updated as well as report back to you when I do come across discrepancies.
Start with some of our most frequented solutions to get help installing your software.