Workspace sync revision not working?

[david.lafleur4MYDQ]

As seen in the in image joined with that post, I'm trying to synchronize my workspace with the current revision available in Vault (assuming "current revision" mean the "latest released").

For testing purposes, I did "get" the released revision "H" of the part "DL002.ipt" and I'm trying to synchronize my workspace in order to get the revision "I" in my workspace, but it seems like it is not working as indented (or I don't understand the real meaning of it). If I'm choosing the "latest version", of course, it works, but the purpose here is the synchronize the workspace with ONLY the released design (A.K.A. validated for production).

Any clarification would be appreciated.

David L.

[Gabriel_Watson]

I think you got everything right. If "I" is the latest released revision, it is marked right there besides de "Released" state column.

You might be confused by the wording, but "historical revision" just means a revision that is part of the history tab in Vault, not historical in the sense of it being old.

[david.lafleur4MYDQ]

@Gabriel_Watson Thank you for your reply.

This is the History of the said part.

As you indicated and that I am aware, the "State (Historical)" is the state the part had at this moment it was logged into the history database and "State" is the live value of the part. Here, I'm simply using "Get" to download on my workspace the revision "H", which then show the little triangle, indicating that my local version is a historical revision of the one in Vault. If I'm trying to synchronize my work space with the "Current Version" parameter selected, it doesn't show me "DL002.ipt" as a valid part to be "Download - Overwrite".

But, if I go back in the configuration and set it to "Latest Version", it does what I would have assume the "Current Version" setting would do.

My goal here is to have only the latest released version of the parts. If I keep the "Latest version" parameter on, it will eventually synchronize to a part that is being worked on right now, which will lead to inevitable problems.

Thank you for your time and if you need more details from me, let me know.

David L.

[Gabriel_Watson]

Oh ok, I see now. Have you tried Actions > Update file reference, and Actions > Synchronize Properties? I just refresh files with those to make sure everything is ok sometimes. Does this happen with more files or just the one?

[david.lafleur4MYDQ]

I tried with different users with different rights in different folders and files, the behavior is the same. I can do the "Update reference file" (which I did), but I cannot synchronize the properties since the parts are released, so are not modifiable. Also, the icon indicating that there is a problem in the synchronization of the properties isn't there (referring to this : ). I also did tests by changing "DL002.ipt" to "Work in progress", which increment the revision but because a "unreleased revision", so the latest status of that part is now a version of revision "J", but the same behavior occurs. And of course, the behavior that is problematic does happen... if I set my setting to "Latest version", it will download the Revision "J" that is in "Work in Progress", which again, works as indented, but not what I'm looking for.

We also already have the Job Process to synchronize the properties done by the job process when we are changing from state to state, so we don't really have to do it manually.

I just feel like "Current Revision" doesn't really mean "get me the latest released revision of this specific file".

David L.

[swalton]

What happens if you check the "Released Biased" option?  

[david.lafleur4MYDQ]

I tested this one as well. The results are exactly the same as just having "Current Revision".

[marina.collet]

Hi David,

I am afraid that you mis-interpret the "Current" in "Current revision".

What this means is that your local file will be updated to the latest version of the revision you have downloaded.

In the attached image I display all versions of my files in the history tab. You can see that I have a file with 15 versions for 4 revisions.

Imagine that I have version 6 on my local workspace. Version 6 is part of the B revision.

Running the "Workspace sync" with the "Current revision" selected will download the released version of the B revision (B revision being the "current" revision in my workspace).

Result: Workspace sync will download version 8.

As a result: if I want the latest released version of my file (in my case  version 13) I will have to use the "Get" function, getting my files one by one......

[david.lafleur4MYDQ]

@marina.collet Thank you Marina for your reply. That clarification should be part of the official website in my opinion.

It is the interaction I feared it would be. Even though I can understand why it exist, I cannot understand why "Updating to the latest released revision" wouldn't be available.

David L.