I've run into this in the past but was reminded of it this morning. Using worksets, lets assume you encounter a user that has already borrowed something you want to work on. If you create an editing request but then close your local file before the request is resolved you can end up the borrower of an element, regardless of the fact that you chose to leave.
This happens if they just Synchronize with Central (SwC) instead of dealing with your editing request directly (meaning Deny your request). The SwC resolves the request internally, which grants your request, making you the new borrower, even though you aren't actively working in the project anymore.
This can be avoided if the person you make the editing request from just denies the request before using SwC. So...yes you can be the borrower even if, "But I didn't do anything and haven't even been in the file for awhile".
This happens if they just Synchronize with Central (SwC) instead of dealing with your editing request directly (meaning Deny your request). The SwC resolves the request internally, which grants your request, making you the new borrower, even though you aren't actively working in the project anymore.
This can be avoided if the person you make the editing request from just denies the request before using SwC. So...yes you can be the borrower even if, "But I didn't do anything and haven't even been in the file for awhile".
3 comments:
Thanks Steve,
another little lighbulb turns on
That pesky editing request. Geesh, who knew?
Hmmm. How about that. Someday, I'm going to look like a Revit GURU when I need to remember this one. THANKS!
Post a Comment