Vault part rename issue

[jon.myers]

We have been seeing an issue periodically when renaming files in the Vault. We have an assembly called control.iam. It has around 15 parts in the assembly. The person working on the assembly has it checked-out, but someone else needs to rename one of the parts, so the person who has the assembly checked-out checks the assembly back in to the Vault. The part is renamed from 99900.ipt to 999XX.ipt in the Vault. Everything looks good. The where used tab in the Vault explorer shows that the assembly now has 999XX.ipt and not 99900.ipt in it. The person who was working on the control.iam now checks the file back out does some work on it then checks the control.iam back into the Vault. A third person who does not have any of the Control.iam parts in their working folder does an open from Vault on the Control.iam, but the resolve file window comes up saying that Inventor can't find the 99900.ipt and it is looking in the working directory of person that checked the file into the Vault. It should not be looking for the 99900.ipt because it has been renamed to 999XX.ipt. This has happened a couple of times. Has anyone else seen anything like this? We are using Inventor and Vault 2008.

-Jon

[Anonymous]

(As you know I am trying to sort out some of these issues too.)

" The person who was working on the control.iam now checks the file back out
does some work on it then checks the control.iam back into the Vault"
- When this person checks the file back out, how does he do it? I believe
this is often where the issues start. I think you must perform an "open
from vault" on the Inventor Menu and absolutely cannot open it from your
local workspace and then check the files out. I also think that control.iam
and all other parent files should be completely deleted from the local
workspace after it is checked in (prior to the rename operation). The
reason for deleting is some people insist on opening from their local
workspace in the future and these parent files will be screwed.

Let me know if it makes a difference for you or if you already do it that
way. I know this may not be the only issue at play here - that is what I am
also trying to nail down.

Thanks!

--
Rob
Inventor 2008 SP2
Vault 2008 SP1
ATI FireGL X2 AGP Pro
Graphics Driver: 8.223.0.0
(2 Monitors at 1280x1024)
Using Direct 3D
Intel Pentium 4 CPU 2.40 GHz
2.00GB of RAM


wrote in message news:5938747@discussion.autodesk.com...
We have been seeing an issue periodically when renaming files in the Vault.
We have an assembly called control.iam. It has around 15 parts in the
assembly. The person working on the assembly has it checked-out, but
someone else needs to rename one of the parts, so the person who has the
assembly checked-out checks the assembly back in to the Vault. The part is
renamed from 99900.ipt to 999XX.ipt in the Vault. Everything looks good.
The where used tab in the Vault explorer shows that the assembly now has
999XX.ipt and not 99900.ipt in it. The person who was working on the
control.iam now checks the file back out does some work on it then checks
the control.iam back into the Vault. A third person who does not have any
of the Control.iam parts in their working folder does an open from Vault on
the Control.iam, but the resolve file window comes up saying that Inventor
can't find the 99900.ipt and it is looking in the working directory of
person that checked the file into the Vault. It should not be looking for
the 99900.ipt because it has been renamed to 999XX.ipt. This has happened a
couple of times. Has anyone else seen anything like this? We are using
Inventor and Vault 2008.

-Jon

[Anonymous]

> "- When this person checks the file back out, how does he do it? I
> believe
this is often where the issues start. I think you must perform an "open
from vault" on the Inventor Menu and absolutely cannot open it from your
local workspace and then check the files out. I also think that control.iam
and all other parent files should be completely deleted from the local
workspace after it is checked in (prior to the rename operation). The
reason for deleting is some people insist on opening from their local
workspace in the future and these parent files will be screwed."

Jon and I worked on this last week and isolated the workflow that causes it.
It happens when someone has a local copy of the of the renamed part and
assembly that uses it and pulls a new copy down from Vault.

The problem is that an .iam opened from Vault in while in Inventor is not
actually overwriting the local .iam so you end up still trying to reference
the old part name instead of pulling the new one. Inventor sees the renamed
part and the local copy of the old name as being the same part. My guess is
that Vault is using the filename as it's identifying reference while
Inventor uses the part's internal file name. Even though the part's been
renamed, it can't tell. For some reason, the user is then allowed to check
the assembly back in, but it's now referencing the old version of the part
from before the rename. (This should not be allowed to happen!!!!)

The "work around" (it really isn't so I hesitate to call it that) is like
you say, to delete all local copies and pull fresh from Vault. However, in
practice this is impractical for us. Often there may be a different
assembly on your local drive that is referencing the renamed part or
assembly so the automatic delete won't happen. It's also way too easy
accidentally check back in the corrupted .iam, especially for novice users.

Patrick