Unable rename files in vault

[spascual]

Hi sirs,

I'm having problem while rename a files in Vault Work Group.

I have found diferences between properties in files that can be renamed and the ones that cannot.

LATEST RELEASED REVISION = TRUE (cannot be renamed)

LATEST RELEASED REVISION = FALSE (can be renamed)

What does it means?????

What am I doing wrong???

Regards

PS: I'm going to perform a reindex task

[john.laidler]

"Latest Released Revision" indicates that the 'version' that you are viewing is the 'released' version of the document.   Therefore, it can't be renamed.

[spascual]

Thanks jclaider, but REVISION property shows WIP value.

I cannont understand, including children and parents.

I will check better.

[john.laidler]

What is the 'STATE' property? 

[spascual]

STATE = WORK IN PROGRESS (WIP)

Include, I have deleted files in vault and check-in again and it runs wrong again.

Ups

Regards

[luttena]

In addition to telling us what the value for the State property is, can you also include a screen capture of the restriction dialog?

Thanks,

Adam

[spascual]

Attached,

Regards

[luttena]

Thank you for the screen capture. That was very helpful. 

The error message that you see is telling you that the part you are trying to rename (10058-003.ipt) is referenced by a revision of the parent (10058-C001.iam) that is released. So, even though the parent file is now in a Work In Progress state, a previously released revision is still pointing to that revision of the part. 

If you create another revision of the part file, then there should be no restriction going forward because the released revision of the parent file will continue to point to the previous revision of the part.

After you've done that, open the assembly file so that it will resolve to the latest revision of the part.

Regards,

Adam

[spascual]

Hi sir,

I'm goin to try it, but I'm telling you that I have deleted al this files from vault and I have done a chech-in, and the problem is still existing.

Regards

[cmcconnell]

Does anybody at Autodesk realize how much work (read money they have cost) they have created for us with the changes that have been made to Vault 2011? Workflows have been destroyed, and performance has been reduced to the point of rendering Vault almost completely useless for a dataset of any size.

This post is a perfect example of a workflow that was changed..

It has gotten to the point that I would not recommend installing Vault, or upgrading from 2010. In fact, I would recommend not upgrading to Inventor 2011 if you use Vault. The improvements in IV 2011 are not worth the hassle and stress you will get with Vault 2011. From what I have been seeing in this group, I am not alone.

We can only hope that when it comes time to develop 2012, they start with 2010 and forget about 2011.

[spascual]

No Reivisions, No Released.

Thanks

[luttena]

Is it possible the part file was used in another assembly file at some point? 

Regards,

Adam

[spascual]

I don't know exactly, but my cistomer have 6819 files with this problem sure

We have done a migration 2 weeks ago and customer has never said something about.

I'm very tired,...

[john.laidler]

We are using the same workflows with Vault 2011 as with Vault 2010, no issues.

To the original poster: 
Can this file be 'checked out'?

[spascual]

Yes sirs,

I would like to repeat that I have deleted this files in vault and added again.

[spascual]

I'm be able to rename files "Released"

Is this the procedure?????

"To rename files, they must be "Released""

[JamesMcMullen]

You should not be able to rename a file that is in the released state.  What is the security setting that you have on the released state?

-Jim

[spascual]

Hi Sir,

I have realized that this problem happens with files that already exist in vault before configure a LIFECYCLE file control.

If we create a new file, we can rename in "work in progress", and we cannot in "released"

With exiting files we cannot rename in "work in progress" and we cannot in "released" (please read first row)

Best regards,

PS: What happens with existing files in vault, once we have configured a LIFECYCLE control??????