Having issues getting the latest version of a file if it's locked (checked out) by another user. Is this a know issue and is there any know solution? Running v13.03.
This looks like it's the issue. Thanks for the info.
Do you mean that 'Get Latest Version' doesn't work, or that it doesn't work the way you expect?
1. What did you do?
2. What behavior did you expect?
3. What behavior did you actually observe?
It doesn't work the way I expect. I can "get latest" on files that are not checked out by another user but if a file is checked out by another user they must either check the file in and leave it unlocked or "undo check out" of the file in order for me to update my local copy. I am a former, actually still, IntraLink user and that vault will allow me update a local copy weather the file is "locked" or not. That is how I would expect EPDM to behave.
Do you think this sounds like that issue I saw on here 2 weeks ago where the EPDM client installation was added from an admin image containing a vault view?
We do use an Admin image for both SolidWorks and EPDM and I'm pretty sure it conains a vault view since every new user is automatically set up locally.
Ken, see if Jim's recommendation is what you are after. If that answers/fixes your issue, then don't worry about what I introduced.
If that doesn't answer your question, consider the admin image could be the problem.
If an admin image contains a vault view, it can hinder user A from getting latest version while user B has it checked out as seen in this thread
Hope this helps
equivaQ Software, LLC.
Ken, if you are imaging systems with a vault view installed that is what is causing the problem. Each vault view requires a unique vault ID number which is generated each time you create a vault view. Imaged vault views will spread the same ID number across multiple users and affect their ability to get latest versions of the part.
Removing the vault view from the client machine(s) and reinstalling it will fix the issue.
Thanks Matt. This was the issue but I forgot to mark Tim's response as correct last Friday. I deleted the local vault view on the affected machines and and then reinstalled them and it solved not only the primary issue but also corrected an issue we were having with updating references.
Are you expecting to see the changes that the other user has made to the file that they have checked out? If so, EPDM doesn't work that way. The 'Get Latest Version' feature simply synchronizes your local copy with the latest version on the server. All changes are made locally and not until the file is checked in (and the version incremented) are those changes available to other users.
If you are just trying to get the lastest version from the server (without any changes the other user has made) and that isn't working, then there is something wrong.
No, I am not expecting to get the local users updated verison. The only way I can do that is to log in as the Admin. I understand the functionality. What I want to get is the latest version stored in the vault on the server not the local users "vault view". I know there is something wrong which is why I posted the question. I was looking for insight on how to correct the issue. For example, if the software needs to be individually loaded versus being loaded from an Admin image I could test it on a couple of users to see if it corrected the issue.
Let us assume that there are 3 state in a workflow naming "State1", "State2" & "State3", and there are 2 users, naming "User1" and "User2".
Now user 1 has checked in a file in state1. now the version of the file is 1. user 1 sends th file to state 2, does some modification, and now the verison of the file is 2. after that usre1 sends the file to state3.
Now if the user2 has only "read file content" rights on state1 & state3. Then user 2 wont be able to get the version 2 of a file, after doing get lattest version too.
Good deal Ken, glad you got the correct answer
Retrieving data ...