When copying detail components that have type mark info associated with them from one project to another, sometimes the type mark stays with it in the new project and sometimes it doesn't. I'm trying to avoid having to re-tag these components when copied to another project. If there is a way to create a type mark parameter within the family, that would solve my problems. I've seen some things online about setting up a shared parameter for this purpose, but I can't seem to make that work (it needs to be explained in more detail). Any suggestions would be appreciated.
It sounds as though the projects in which the type mark disappears does not have the corresponding Shared Parameter loaded. Look at the detail component family as well as the detail item tag, and make sure that you know which parameter it is.
Manage>>Project Parameters>>Add>>Shared Parameter
This will take you to the Shared Parameter TXT file. Locate the required shared parameter. Associate it to Detail Items by checking Detail Items in the panel to the right of the dialog box.
...I'll just add here, that I wouldn't add a Shared Parameter with the name "Type Mark", as this is a built-in Shared Parameter use in the majority of Revit Templates. If you were to add another; you'll have 2 with the same name in the project -- and no way of knowing which "Type Mark" is which.
When I tried this I was able to see the shared parameter in both projects, but I don't know how to make it act like the "type mark" parameter. Whatever I type into the new shared parameter box in the properties doesn't translate to the detail item tag when used, like the "type mark" box does.
If "Type Mark" is already a shared parameter, how do I get it to show up inside a detail component family?
TYPE MARK automatically added at the Project Level. If you want to add your own Shared Parameter in the family itself, I was just cautioning you about naming it TYPE MARK, because you'll end up with 2 in the Project.
@Anonymous wrote:
...but I don't know how to make it act like the "type mark" parameter.
You can't.
@Anonymous wrote:
When copying detail components that have type mark info associated with them from one project to another, sometimes the type mark stays with it in the new project and sometimes it doesn't. I'm trying to avoid having to re-tag these components when copied to another project. If there is a way to create a type mark parameter within the family, that would solve my problems. I've seen some things online about setting up a shared parameter for this purpose, but I can't seem to make that work (it needs to be explained in more detail). Any suggestions would be appreciated.
Yes you can't by nesting a Generic Annotation with a label reading Type Mark parameter in the family. But it is a bad idea. Think about what you would see if families got flipped.
@Anonymous - detail components have Type Mark as a built-in parameter. I did duplicate the problem, and the tag read the value of the type mark correctly (and I did not need to re-enter the value) when I copied the component from one project to the other. Where did you get the tag from? Use the OOTB Detail Item tag.
I have come to find that when I copy one individual detail component to another project the type mark still works fine when tagging. However if I have a detail component that has multiple types, while the first one I copy retains the type mark, some of the other types do not.
Let me clarify what I'm trying to do. When loading a detail component family into a new project, there is no type mark associated with it, so it will not tag. I don't want to have to manually enter the type mark info every time I load a detail component into a new project. So I thought that I would just copy them over instead of loading the family, but some of the types within the family don't retain the type mark info, like I mentioned above.
So I need to figure out why some of the types within the family don't transfer the type mark info, or I need to find a way to include the type mark info into the family itself, so that I could load the detail component into a new project and tag it with the type mark info I already assigned to the family, if possible.
@Anonymous wrote:
I don't want to have to manually enter the type mark info every time I load a detail component into a new project.
You don't need to manually enter it for every instance of the same detail component in the project; it's a TYPE parameter. It applies to all the instances of the Type.
That said, why would you want to transfer Type Marks between Projects? Type Marks are project driven. For instance, look at the Type properties of all your Windows in the Project Browser. Notice they all have been assigned a unique Type Mark. If 2 of them shared the same Type Mark, Revit will post a warning until it's resolved.
If you have multiple components of different types in the project, that you want to quickly assign a different Type Mark to all of them simultaneously, Revit have a tool for this: Element Positioning under Tools on the Extension Tab.
Is this what you are talking about? Take a look at the three files (where tagged detail components have been copied and pasted).
barthbradley - I understand it's a type parameter. When I said I didn't want to enter the type mark info every time I load a detail, I meant different detail components not the same one. I want to transfer type marks between projects because most of the detail components we use to fill in our wall sections, roof details, etc. are going to be tagged the same in every project. A detail component for a metal stud track, mortar net, wood blocking, etc. will always be tagged the same.
rsahayUZMK9 - sorry, we are still in Revit 2016, so I can't open those files.
Yes, I get it now. It least I think I do. Basically, @Sahay_R is showing a viable solution. She's created a Shared Parameter in the family to identify the family type, and has a tag that reads that Shared Parameter value stored in the family. The Shared Parameter should be consistent among projects, because it's in the Family. You could do basically the same thing by having a tag that reads the "Family Type" name parameter.
As far as for why you are losing that information between projects, I think she hit the nail on the head with her post. Assuming the family AND the Tag are correct, and the error happened on copying the family between project envirionments, you might try this: Highlight the Family in the Project Browser and click on Reload and reload the family from the family.
Yikes! @Anonymous - what a blast from the past! Here it is in 2016.
An alternative to creating the shared parameter as I did would be to populate Type Comments, and doctor the tag label to talk to that parameter. Whatever floats your boat.
Ok, I finally understand how all this works. Part of my confusion was in applying the shared parameter to the detail item tag family. I have multiple labels within the family for different length text and didn't realize I didn't apply the shared parameter to each label. Nevertheless, I really appreciate everyone's help, as well as the revit files that were posted.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.