Showing posts with label Insert from File. Show all posts
Showing posts with label Insert from File. Show all posts

Friday, November 06, 2020

Insert From File and BIM 360

When we're working on a BIM 360 hosted project there are times we'd like to use the Insert From File > Insert Views tool. Unfortunately BIM 360 isn't an available path in the Insert From File dialog.

Yes, we can download a copy of the project or open both projects and use Copy/Paste but it would be nicer to be able to use the tool itself as it is an easier/faster (more obvious) process.

Monday, May 15, 2017

Insert From File and a Worksharing File

I bumped into a subtle conflict this evening. I created a new file from a stock template. I then used Insert from File > Insert Views from File to acquire a few drafting views. When I closed this new project and decided to open the file the harvested drafting views are stored in this message appeared.

Keep in mind that no files were actually open at the moment. I was looking at the Recent Files list yet when I attempted to create a new local file for the project I just used Insert From File on the message popped up. This means that the file is technically still open in RAM as far as Revit is concerned, it's just not open for me to interact with.

I had to exit Revit so it could relinquish its hold on the file before I could start Revit up again to get back to work.

Tuesday, October 18, 2016

The Family has been Renamed

This warning message is probably familiar, troublesome and annoying.

I was reading a couple threads at RFO; THIS ONE and THAT ONE.

Apart from workset related issues I've written about before, I believe the underlying cause of renaming is that Revit perceives a family as different. That's not very surprising but I think that the actual difference is the result of different versions (2016 vs 2017) or having Save As used on the family (to put it in a different folder)...AND any operation that involves Copy/Paste, which includes the Insert from File tools.

When Load from Library > Load Family is used I only see it occur when worksets are being used (see the links at end of this post). The families merely having some different parameters (either instance or type) generates the dialog asking how we want to deal with the existing definition.

Using Revit 2017.1 and passing a family from one project to another I observed the following:

Family is renamed but no warning message:
If the family being introduced is an older version (upgraded) of one already in the model
If the family is same version but has had Save As used on it, i.e., to put it in a new folder location

Family is renamed and the warning appears:
If the family is an older version or Save As version AND Insert from File is used

Family is not renamed:
If the Family is copied from same library folder to a new folder
If the Family is from the same library folder
If the Family (existing) is reloaded from older version before using Copy/Paste or Insert from File.

The issue can be avoided if we are meticulous about using families from the same library and version. If we load office details from a detail library project file using Insert from File and the families (some or all) involved are based on older versions while newer versions are already present in the project we'll incur the renaming penalty.

The detail library should be updated, have the newer versions loaded first so they will be the same as those in the active project. If we need to keep the detail library in more than one version then we'll have to decide how to manage that and for how long. Merely upgrading the detail library model does not appear to be sufficient to avoid the issue.

I ought to mention that I can load a family and let it upgrade. Then if I use Copy/Paste to pass it along to another project file it does not get renamed unless the existing family in that project is based on a different version than the one I just upgraded. Upgrading a family does not seem to create the same problem that using Save As does for a family, at least not in the context of Revit treating it as a rogue family competing for the same name/existence in the project.

Regarding the workset issue I wrote three posts about previously, they describe how families can get renamed when worksets are being used and more than one person loads the same families and synchronizes their work in a specific way. The posts are:

FIRST post
THIRD post (references the first two as well)

Sunday, March 29, 2015

Wish - Insert From File - Work with Templates

Insert from File allows us to import views from another project, views like schedules, drafting views or even sheets that contain either. It is biased toward RVT files though.

It would be handy if it we less biased, enough to include RTE (Revit templates) too. Since we probably have standard stuff set up there anyway. Doing so would allow me to acquire a view from a template file instead of having to first save one as a new project or find another project that is already available in a project folder elsewhere.

Tuesday, April 29, 2008

Insert from File

This feature is intended to allow us to acquire information from another project file and add it to our current project. There are two methods, Views and 2D Elements. Both methods involve selecting a project file first. To get started you choose the File menu and then Insert from File.

The first option, Views, grants us access to views and sheets. The catch is the views are 2D views like drafting, detail and schedule views as well as sheets. The sheets must either be empty or contain only 2D views. In the past I posted an article describing using this to deal with dummy sheets to fill out a complete drawing list. This feature presents us with a dialog listing the eligible views.

It is a great way to transfer office standard detail sheets and schedules into a new project. When you select a sheet that includes just 2D views Revit will bring the sheet and all the views on it into your project as well as placing them on the sheet.

For campus projects that share details it allows you to place copies of the details in each building file so you can create intelligent view references to the details. If you only change them in the "master" file (a primary building model project) you only need to keep the sheet and detail numbers coordinated if you do all printing from the "master" project file.

The second option, 2D Elements is intended let us "steal" drafting annotation, detail lines and detail components from model views. Imagine a wall section that is the same or very similar to the one you are working on now. Using this tool you can grab the 2D embellishment in the other project and added it to your current model's view. This tool presents a dialog of eligible views too, all views that have any 2D information added to them.

Annotation that requires a reference like dimensions or tags will likely fail to insert for fairly obvious reasons, namely the reference isn't necessarily in the same location or even present.