Prevent Component Deletion from Model

[LisaDrago]

Hello!

I was wondering if there is a way to lock or somehow prevent a component from being deleted from a model?

A little back story on this - we have a family that is continually being deleted from a model. we don't know whom is doing it as it is on multiple projects. It is another discipline doing it, but again - we don't know whom. We have tried pinning it and placing it on a workset that is checked out. Neither of those stop the component from being deleted from the Families listing.

Is there anything anyone can think of that could help us?

Other then finding the person whom is doing this and *fix* them....

Thanks for your thoughts.

Kind Regards,

LD

[ToanDN]

If it is under a checked out workset and still getting deleted than something else is going on. What family is it and can you share it?

[LisaDrago]

Well - we have run several tests... with it pinned and then on the locked workset (not locked by me) and from the Project Browser, Families - I can go in that list and delete it. That is the only way it can be done because its just not 1 missing - all of them are gone.

Now I know that is a person issue - and they are ignoring the warning that there are 14 of them in the model - do you still want to delete?

Just trying to get around the person and protect our work.

I have attached the family we are using.

[hmunsell]

this hasn't happened in my office for a while now. but last time it happened it was because someone was deleting rows from a schedule. i only found them because it was happening frequently enough that the effected staff were able to tell me next time it happened, almost eminently. i was able to track them down by going thru the SLOG file and finding who was in the model and then going thru users journal files. 

Then we made the needed adjustment to the staff that was "editing" the schedule :-).

[LisaDrago]

thank you @hmunsell -

But only if it was that easy. These are not scheduled.  

They way we are finding them is after we have submitted for cd's and go back in for a fresh set of pdfs' and then they are gone.

Very frustrating and embarrassing in front of a client to say the least.

[hmunsell]

if you have things on checked out worksets and there still deleting them, there doing it deliberately. There probably saying to themselves "who keeps locking this workset....". old trick we used back in the day was to make a user account called DO NOT DELETE. Log in under that account and lock the workset(s) using that account. then close the model and don't relinquish. log back in as you and the workset is locked to a non user account.  they can still get around it if they know how, but at that point they have no excuse. 

i dont know how many people you have there, but have you considered checking everyone's username settings in Revit (Options > General> username)? To make sure there all signed in as who there supposed to be. i have had that issue when fixing a central model and left it logged in as someone else on accident :-). 

[TripleM-Dev.net]

So between submitting for cd's and making de pdf's they get deleted?

How much time is between them?

Have you tried creating a new Central File, maybe somebody's local file is corrupt, or the family and revit is reparing it by deleting the erroneous family by auditing? just guessing.

So it doesn't need to be deliberat, but depending the number of central file backups find consecutive backups with and without the element, and see which useraccount sync'ed it. (see Central File history for the Sync moments.)

Good luck tracking this down.

- Michel

[ralvarez1976 · Accepted solution]

You need to check out the family's workset, not the elements.

1. Open the model with a "DO NOT DELETE" user or similar.

2. Go to the "Worksets" dialog accessible from the bottom of your screen.

3. In the lower left of the "Worksets" dialog box, uncheck "User-Created" and click "Families."

4. In the list that comes up, find your family's workset, which will have the same name as the family. Select it and click "Editable."

5. Click OK to exit this dialog box.

6. Sync to Central, but make sure to uncheck "Family Worksets" first.

7. Close the local file.

Now that specific family's workset is locked out for all other users, other than "DO NOT DELETE."

[LisaDrago]

Thank you for your help.

Totally forgot about locking down the family itself.

We will see if this helps us moving forward or if there is something else going on - like model corruption.

Thanks again.

LD 

[LisaDrago]

All the tracking down would be our next bet.

Will see if locking down the family itself will work - or if it is model corruption.

if it is corruption - then locking family down won't make a difference.

Thank you for your help!

LD