Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Duplication of detail families when inserting a view from a file.

38 REPLIES 38
Reply
Message 1 of 39
haydenwse
2751 Views, 38 Replies

Duplication of detail families when inserting a view from a file.

When I load 2d details by "inserting a view from a file" from my detail library, it gives new names to my standard detail components.  I get a warning message such as “Family "CMU Standard" has been renamed to "CMU Standard1" to avoid conflicts with the existing Element.”.  THERE IS NO CONFLICT BECASUE THESE FAMILIES ARE EXACTLY THE SAME.  Smiley Mad

 

It is hard enough finding the correct detail component with a list over 100 long without unnecessary duplication.  Is there any way to prevent this duplication? 

38 REPLIES 38
Message 2 of 39
JSmith33
in reply to: haydenwse

Thank you for the post.  While this is not a solution, I wanted to let you know that the Autodesk development team is aware of this issue and is researching a fix/workaround.  Similar cases have been escalated to their attention. 



Jeremy Smith
Revit Support Specialist
Autodesk, Inc.

Revit Clinic



Message 3 of 39
haydenwse
in reply to: JSmith33

It would be very helpful if it would notify you of the potential conflict and allow the user to except the new name or use the existing family.

Message 4 of 39
jasonmccool8686
in reply to: JSmith33

So... 6 years later, and I keep having the same frustrating issue.... Did the development team ever fix this???

Message 5 of 39
ToanDN
in reply to: jasonmccool8686

Since @jsmith33 latest activity is on 9/20/2010 I doubt it very much.
Message 6 of 39
jasonmccool8686
in reply to: ToanDN

Well, I kinda was hoping that Autodesk's work on developing a "fix/workaround" wasn't tied to one particular employee.Smiley Wink Maybe finally getting a semi-usable text editor in Revit 2017 after 10 years spoiled me and gave false hope that this issue had also gotten somewhere in the intervening years.

Message 7 of 39
haydenwse
in reply to: jasonmccool8686

To the best of my knowledge they have never fixed this and it is still a great frustration.  my work-around is to use the one element that can be placed on multiple sheets, the legend.  I create my prototype detail and then use the "freeze" command from the extensions to make it a 2d drafting view.  I then clean up the resolving mess and copy the detail to a legend which I can insert on each piece drawing.  Then I created a detail component that looks like a section tail which I assign a mark name to match the legend and tag it with a tag that returns the mark name. 

 

In other words, it SUCKS!

Message 8 of 39
jasonmccool8686
in reply to: haydenwse

Yikes! Smiley Surprised That does suck...

 

C'mon, Autodesk: throw us a bone here! 

Message 9 of 39
haydenwse
in reply to: jasonmccool8686

I am not a Revit programmer but given that they can have sections and callouts that reference others it shouldn't be all that difficult to make views that reference others.

Message 10 of 39
JasonLLINDNER
in reply to: haydenwse

 

 

For heavens sake! It's a view NOT JUST A DETAIL family and NOT A CALLOUT TAG REFERENCING ANOTHER VIEW. It is the worst view of all, one with 100 families! Which could be 100 outdated detail components/families

 

Besides why would you be bothered by REVIT renaming an inserted view and it's components but not bothered when it renames when you duplicate it in the project!? What is the next wish? Have two sheets same number?

 

What if one of the components on that view is different from an existing! How would you expect REVIT to know? You want it to prompt? So if a view has 100 components of similar names it prompts 100 times for each component? Great idea

 

You can't have 2 views/families same name. period lol. either delete one and its components before you insert views or live with it. 

Message 11 of 39
ToanDN
in reply to: haydenwse

We were talking about detail component families, not views. You need to chill dude...
Message 12 of 39
haydenwse
in reply to: JasonLLINDNER

My bad, I should have read my original post better, I was responding to another of my pet peeves of not being able to place a typical detail view on multiple sheets for use in precast shop drawings.  I will typically have upwards of 100 piece drawing sheets that need to have the same typical details on them and it would be nice to be able to place these typical views on multiple sheets.

 

On the issue of getting multiple versions of the same 2d detail family I still have this problem as well and it is very frustrating.  As an example of the renaming issue, I have a simple detail family for dimensional lumber in section that makes a #2 rectangle with 1 diagonal #1 line for blocking and a second for continuous framing and it is named "lumber section"  If I insert a drafting or detail view from my typical details that has this family in it, it will be renamed "lumber section 1".  If l load another view it will get named "lumber section 2", etc. so-on and so-forth... 

 

I have enough families in any given project that this duplication is very frustrating.  I eventually go into a dummy view and place the bogus details and do a "select all" and change them to the original family but what a pain.   

Message 13 of 39
ToanDN
in reply to: ToanDN


@ToanDN wrote:
We were talking about detail component families, not views. You need to chill dude...

oh @JasonLLINDNER you are such a quick editing ninja 😉

 

Original post for context of my reply.

 

Capture.PNG

Message 14 of 39
ToanDN
in reply to: JasonLLINDNER


@JasonLLINDNER wrote:

 

 

What if one of the components on that view is different from an existing! How would you expect REVIT to know? You want it to prompt? So if a view has 100 components of similar names it prompts 100 times for each component? Great idea

 


Revit is a Database program.  It should know enough information of any objects to determine the differences.  It is reasonable to expect Revit to manage manage duplication better than just adding a new suffix to everything.

Message 15 of 39
haydenwse
in reply to: ToanDN


@ToanDN wrote:

@JasonLLINDNER wrote:

 

 

What if one of the components on that view is different from an existing! How would you expect REVIT to know? You want it to prompt? So if a view has 100 components of similar names it prompts 100 times for each component? Great idea

 


Revit is a Database program.  It should know enough information of any objects to determine the differences.  It is reasonable to expect Revit to manage manage duplication better than just adding a new suffix to everything.


EXACTLY!

Message 16 of 39
JasonLLINDNER
in reply to: haydenwse

I will add a reminder to my calander andi will revive this post in 6 years. I may be relatively new to REVIT but I've been working with VB, SQL and DDL for the past 7 years !!! And what you two have just said is ...hmmm 

 

Well let's just say if REVIT is the database software you say it is it would have taken AUTODESK less than a 6 days to implement the option you are requesting not 6 years...But again what can one say! You know better 🙂 just not about database

Message 17 of 39
Meelis123
in reply to: JasonLLINDNER

January 2018 and no fix.

 

There is actually a workaround for this. Well, sort of. Create a type catalog. Every change you make you do there. Then load the family and select types you need or changed. Revit overwrites all values. Without prompting by the way. So be aware!

Message 18 of 39
jasonmccool8686
in reply to: Meelis123

Meelis123, I'm not sure I'm following you there. Could you maybe explain your procedure a little more?

Message 19 of 39
Meelis123
in reply to: jasonmccool8686

Ok, this is what I did:

 

I had two models, let's say, Project 1 and Project 2. I wanted to transfer window types from Project 1 to Project 2. The problem was that I had already done that once by using simple copy & paste from clipboard option. Second time, after some minor changes in Project 1 I tried to do that again and it gave me this stupid "the loaded type has been renamed to blah blah blah" error since those types already existed in the project. As usual. No matter if there is any difference or not it just duplicates them anyway.

 

So I went to Project 1, selected the window family, then File > Export > Family Types and saved the txt file to my window family catalog with the same name as this window family. So regular type catalog creation process.

 

Then I went to Project 2, clicked Load Family, selected the window family and the type selector window appeared as normal. I selected the types (which already existed in Project 2) and loaded them. Revit did not warn me or anything about existing types. It just rewrote every value that was available in the type catalog.

 

However, saving type catalog did not add <Family Type...> parameters to the txt file, that's a known issue. So I lost this information. It can be added later manually to the type catalog however. So it seems that if you have a multi model project and you want to syncronize family types between the files, a type catalog is the answer.

Message 20 of 39
Meelis123
in reply to: Meelis123

Although I must add that when you want to insert views from another file like in the original post, the type catalog does not help.

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

Post to forums  

Rail Community


Autodesk Design & Make Report