Recent Files and Worksharing

Just don't do it. Don't use the Recent Files page/list if you are actively working on projects that use worksets (worksharing). Why? All too often I find people click on the links that are offered there instead of clicking Open to browse to the location of the Central File to create a new local file.

The Recent Files page that opens (if you let it) will offer you the last few files you worked on. If you closed your local file last night then that's the file it will offer you in the morning. I've always encouraged people to make a new local each day, in fact I just make a new local every time now regardless how many times I leave and return to a project. When you click on the link on the Recent Files page you'll be opening your local file from yesterday. Is it the end of the world? No but the larger the team and the bigger the project the less I want you to do it. The more moving parts the more chance that working with dated local files can introduce a conflict.

If you just created the central file then the file offered is actually the central file. Clicking that opens the central file without asking about a local file at all. I've seen that happen several times. The person that just created a central file ends up working in it and then other people get started in their local files. When the person in the central file tries to synchronize they get the message that they must Save As to create a local file first. Confusion sets in for a moment and then they realize what happened...or they ask me what happened and we realize what happened together.

When I'm working on projects that use worksets I only use the Projects > Open link if the Recent Files page is being used. I could use the Application menu > Open or just click the little Folder icon on the Quick Access Toolbar.

Once I've got the correct central file located I just make sure the Create New Local option is checked and off I go. Oh, I also make sure I choose the Specify option so I can decide which worksets to start with. My local file will open a lot faster if I'm selective.

I say "just say no" to the recent files page. (when worksharing is involved)

Parts and Linked Files

When Parts as a feature appeared in 2012 it didn't support creating them from elements in a linked file. When 2013 came out it casually mentioned that it could do so in the last line of the "what's new..." text regarding Parts.

Parts can now be made from loaded families (such as Columns, Structural Columns, Structural Framing, and Generic Model) and from originals in a Revit link. (my emphasis added)

Perhaps this willingness to work with link elements could be leveraged for some sort of coordination approach as compared with the Copy/Monitor tool?

As it happens, Desirée Mackey with Martin/Martin is presenting a class (lab format) at RTC next week called "The Prolific Potential of Parts". I'm looking forward to hearing what she has to say!

Beam Joins

Quick tip Thursday: The shortest beam in a join will force the longer beam(s) to cutback. In other words the shorter beam will not cut back. We can use the Beam/Join Editor to adjust relationships.

Visibility Graphics Dialog and Using Current View Only

Revit 2014 introduces an enhancement regarding importing CAD data (I believe undocumented). During an Import of CAD, in the past when we used the option "Current View Only" Revit showed a reference to that link in the Visibility Graphics dialog (V/G) regardless of the view we were working in.

With Revit 2014 it now filters out the link in views that it was not imported into. Naturally if you use Copy to Clipboard and Paste Aligned to put a copy in another view Revit will start to include the link in the V/G dialog again. This is what you should see if you use Current View Only for the import.

CASE Apps Go Pro

CASE is desperate to gain new subscribers, so desperate that they are resorting to easter eggs. Very funny image will greet you if you follow the advice at the end of their post. I was tempted to give it away but decided not to at the last moment, tease...

Synchronize with Central and Referencing Elements in Linked Files

A post yesterday at RFO reminded me I've not written about this situation before. Generally Revit supports applying dimensions to elements that are in linked files (tagging too). If we go down that road a paradox of sorts can occur as several of us are working. RFO member AnthonyB did a nice job of explaining the conditions he encountered. The following is based on his example, applying dimensions to linked walls:

Model A has walls and Model B has dimensions. Larry adds some new walls to Model A and uses Synchronize with Central (SwC). Then Larry opens his local copy of Model B and adds dimensions to his new walls followed by using SwC.

Meanwhile Darryl already had his Local File of Model B open doing other things and Larry's changes all happened while he was working in this file. When Darryl uses SwC to share his changes he gets a warning message like this one.

Further, since Larry added a couple tags on walls, in the link, Darryl's message includes something like this one. The host elements (walls) are not present so Revit wants to toss the tags too.

We must take extra care when we choose to reference elements in linked files. If your project uses this approach you'll need to let others know that they should use Manage Links, select each affected link and click Reload BEFORE using SwC. This will ensure the elements that your current project file is supposed to see, will be. Be careful out there!

Moving the Project Base Point

David Baldacchino tweeted today that he has proof that Revit doesn't like geometry far away from the origin of the project file, specifically 10 mile radius from the origin. He provided an image of this warning message.

I have to admit I've never tried moving the project base point that far. I guess I've been indoctrinated to play inside my 10 mile radius sandbox? Be prepared to get your hand slapped by Revit if you try it.