Community
Vault Forum
Welcome to Autodeskā€™s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results forĀ 
ShowĀ Ā onlyĀ  | Search instead forĀ 
Did you mean:Ā 

Purge file versions only by Admin or Doc-Editor-II is enough?

10 REPLIES 10
Reply
Message 1 of 11
Maxim-CADman77
388 Views, 10 Replies

Purge file versions only by Admin or Doc-Editor-II is enough?

Both wiki-help (http://wikihelp.autodesk.com/Vault/enu/Help/Help/0170-Administ170/0205-Client_A205/0207-Administ207/...) and local help (http://crackingthevault.typepad.com/crackingthevault/2013/09/autodesk-vault-help-for-2013-and-2014.h...) state that Document Editor II role (guess it is about "Document Editor (Level 2)") is enough for performing file version purge.

But "Purge fles" action is absent from the list of actions for this role.

 

I wonder does it mean the help is misleading and only Administrator could execute Purge on files?

10 REPLIES 10
Message 2 of 11

Week have passed. Case 08818675 was auto-created but nobody from tech-support seems to be even bothered.
Unfortunately I should admit that such Vault support team attitude become usual nowadays.

Message 3 of 11
herrerh
in reply to: Maxim-CADman77

I think the Purge File Versions Role is for the Administrator only and is for purging through the ADMS Console.

 

In the client interface, if you have delete rights (Doc Ed 2), then you can purge in the Vault client on individual files.  Not globally.

 

-Hywell

 

 



Hywell Herrero
Data Management Support Specialist
Product Support
Autodesk, Inc.
Message 4 of 11
Maxim-CADman77
in reply to: herrerh

Thank for your reply.

But then I have another question - what might be reason that Purge
command being executed on IDW by person with DE2 role (with full access
to the file) leads to Error303 "You do not have adequate permissions to
perform this operation"?

File is of Base category (not associated with Item, not in released
state or anything like this).
Message 5 of 11
herrerh
in reply to: Maxim-CADman77

Have you checked to make sure that there aren't any permissions on the file?  Or Folder restrictions at the folder level?

 

I ran through the process on my Vault with a DocEd2 user and did not get a 303 error.

 

-Hywell



Hywell Herrero
Data Management Support Specialist
Product Support
Autodesk, Inc.
Message 6 of 11
Maxim-CADman77
in reply to: herrerh

The user could edit file (property). And this creates new version.

Could it be counted enough checking?
Message 7 of 11
herrerh
in reply to: Maxim-CADman77

I don't believe that deletes the file.  If you add a new fiel to the vault, version it i few times, try purging against that.  Make sure that you are able to delete the file as well.

 

-Hywell



Hywell Herrero
Data Management Support Specialist
Product Support
Autodesk, Inc.
Message 8 of 11
Maxim-CADman77
in reply to: herrerh

I act as follows:

1. Create copy of the IDW in the same folder (Copy Design command
was used).

2. Successfully delete the original IDW.

3. Edit property f the copy several times which led to creatig
several new versions.

4. Run Purge command on the copy ... just to get Error 303.
Message 9 of 11
olearya
in reply to: Maxim-CADman77

Hi Maxim,

 

Please make sure that purge is enabled on your Vault.



Allan
Product Manager
Autodesk, Inc.
Message 10 of 11
herrerh
in reply to: olearya

LOL, I forgot that one detail to check.

 

-Hywell



Hywell Herrero
Data Management Support Specialist
Product Support
Autodesk, Inc.
Message 11 of 11
Maxim-CADman77
in reply to: olearya

That's another unclear question.

In SP1 for Vault 2013 Autodesk disabled purge and gave recommendation to
fix all references with ARRU prior to re-enabling purge.

I was honestly trying to fulfill the recommendation but ARRU refused to
work in our environment. It took me several cases (and months) to
persuade Autodesk to fix ARRU. After all ARRU was fixed but occurred to
be useless in fixing about 10000 entries in our database.

I tried to get further recommendation and was told that I as vault Admin
should communicate with author of each and every file containing
dangling relationships to decide which file to write as lost
reference... I was chewing it over but meanwhile we moved to 2014 ...
and here it is - purge command is no more grayed out. I thought it means
Autodesk decided to enable it but you words make me unsure....

Well I tried to run it inside console and got message that purge is
disabled. Attempt to run purge by Administrator also leads to 303

Now I have two more questions:

1. Isn't it confusing that purge command is not grayed out in file
context menu in VE2014 (not sure but think it was grayed when server was
2013)?

2. Could purge be enabled with 10000 dangling relationships in
database?

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report