topic Re: Purge & losing files in Vault Forum

Purge & losing files

johan.degreef — Fri, 01 Apr 2022 17:29:17 GMT

Is there any way you can loose parts or assemblies with a purge command on the ADMS console. If you use purge with or without lifecycle controlled files. And losing means last versions of files that are used somewhere.

We had an issue were 2 people were working on the same project, and at some point a few subassemblies were gone. The constraints were still there, but the assemblies and parts were gone. The constrains were corrupt because of the missing parts.

The only thing that happened between good/bad, was a purge on Friday evening. We could check shared views from a week back that the parts/assemblies were actually there at that time. So we are all confused at what happened - it was not the first time this occurred neither.

Re: Purge & losing files

ihayesjr — Fri, 01 Apr 2022 17:52:41 GMT

@johan.degreef

Are you sure the components were the last version?
Were the components in a Lifecycle Definition?

For all components that are Lifecycle controlled, the state control determines what can or cannot be purged.

For all components that are not Lifecycle controlled, the purge configuration determines what can be purged.

However, the purge based on versions has rules outlined in the Help.

Vault 2022 Help | Purging Versions | Autodesk

Re: Purge & losing files

johan.degreef — Fri, 01 Apr 2022 18:46:50 GMT

@ihayesjr wrote:
@johan.degreef
Are you sure the components were the last version?

Don't know if I understand that - isn't there always a latest version of a component (component = part or assembly?)

@ihayesjr wrote:
@johan.degreef
Were the components in a Lifecycle Definition?

All our parts and assemblies get a (default) lifecycle - based on the OOTB flexible lifecycle. The missing ones could have been in the "Work in progress" state.

Reading this from the help ensures me that no file can be completely deleted, right? On the other hand delete does not mean removed from an assembly.

Basic rules of purging:

The latest version in a revision cannot be purged (this revision is never removed). To remove a file and all of its versions from a vault, use Delete.
The leading version of a revision cannot be purged.
File versions linked to items in Vault Professional cannot be purged. To remove a version linked to an item, the item must first be deleted from the item master.
File versions that are labeled cannot be purged.
File versions marked as Controlled by the life cycle definition may not be purged.
Only the first, last, or first and last versions in a released state can be purged.

Re: Purge & losing files

ihayesjr — Fri, 01 Apr 2022 18:53:00 GMT

Ok,

Forget the first question since all your files are controlled by the Flexible Lifecycle Definition.

In the Work in Progress state, you may have left this setting in the Control Tab.

It states "All versions in this state will be removed during a purge, except the first and last version in each series."

Therefore, if you have 10 versions in Revision A, versions 2 - 9 will be purged.

Re: Purge & losing files

johan.degreef — Fri, 01 Apr 2022 19:08:49 GMT

Work in progress is set to 1st and last, but released state is set to all...

Re: Purge & losing files

ihayesjr — Fri, 01 Apr 2022 19:08:45 GMT

So in the Release state, all versions in that state will not be purged.

In the Work in Progress state, the first and last versions in that state will not be purged.

Re: Purge & losing files

johan.degreef — Fri, 01 Apr 2022 19:32:01 GMT

So my conclusion here is, purging controlled or not controlled by lifecycle from the ADMS, it couldn't have caused the subassembly and parts missing from the main assembly.

Re: Purge & losing files

ihayesjr — Fri, 01 Apr 2022 19:49:56 GMT

According to your settings, there should have been a version of the sub-components still in Vault.

Re: Purge & losing files

johan.degreef — Sat, 02 Apr 2022 10:56:50 GMT

@ihayesjr wrote:
According to your settings, there should have been a version of the sub-components still in Vault.

Still in Vault, but out of my assembly (only the corrupted constrains were left)