Revit 2025 not bringing family parameters when copying elements from another family

[Ambrose.Clark]

In Revit 2024 and previous, if you copied an element from one family to another, such as a label, linework, filled region, etc. Revit would automatically bring over any visibility parameters (checkboxes) with the element. This was especially helpful for bringing titleblocks up to our company standard, by copying in things such as our Not For Construction stamp, which automatically brought its visibility parameter with it. Now it does not, and we have to create the parameter manually.

Was this functionality removed intentionally, or is this a bug that will hopefully be fixed?

[RSomppi]

---

@Ambrose.Clark wrote:

Was this functionality removed intentionally, or is this a bug that will hopefully be fixed?

---

I think it's more likely a workflow/content issue rather than functionality being removed.

Can you give a specific example of it working in 2024 and not in 2025? Your description is rather generic. My feeling is it had to do with different project templates not being fully set-up to your standards in 2025.

[Ambrose.Clark]

Here's a good example:

If we receive a title block family from a client to use, we like to copy over our own north arrow, not for construction stamp, etc. from our default company title block family. In that title block, we have instance visibility parameters set up that control the visibility of these items. We also have custom Revit addins that we developed to automate the behavior of certain elements (like the NFC stamp), so the name of these visibility parameters is important.

In Revit 2024 and previous, if we simply copied the NFC stamp text element from our company standard title block family into a different one, the visibility parameter we have associated with it would also be copied over. In Revit 2025, it does not. We have to manually create the parameter, make sure it's named the same, and then associate that piece of text with that parameter. It's a lot more time-consuming. I can see why you might not want that to happen in every instance, but it would at least be nice to make it toggleable behavior.

[RSomppi]

---

@Ambrose.Clark wrote:

In Revit 2024 and previous, if we simply copied the NFC stamp text element 

---

What is that element? 

---

@Ambrose.Clark wrote:

we have instance visibility parameters set up that control the visibility of these items. We also have custom Revit addins that we developed to automate the behavior of certain elements (like the NFC stamp), so the name of these visibility parameters is important.

---

What kind of parameters are they, shared, project?

---

@Ambrose.Clark wrote:

In Revit 2024 and previous, if we simply copied the NFC stamp text element from our company standard title block family into a different one, the visibility parameter we have associated with it would also be copied over. In Revit 2025, it does not. We have to manually create the parameter, make sure it's named the same, and then associate that piece of text with that parameter. It's a lot more time-consuming. I can see why you might not want that to happen in every instance, but it would at least be nice to make it toggleable behavior.

---

Have you compared project templates for each version? Maybe those parameters were stored in the template as project parameters. The fact that you have to make them again leads me to believe that they were project parameters that are added to elements as they are inserted as opposed to being stored within those elements.

[Ambrose.Clark]

The element is a text field.

They are family parameters.

This isn't about a project, this is copying elements from one family to another family, specifically titleblock families. I tested this using the same titleblock family. All I did was upgrade it from Revit 2022 to both Revit 2024 and Revit 2025. In Revit 2024, the family parameter controlling the text field's visibility was copied into the new titleblock with the text field. In Revit 2025, it was not. We tested this across multiple files and multiple different elements (lines and filled regions as well). Family visibility parameters do not copy with the element they are associated with anymore.

[RSomppi]

I'm not using 2025, so if their is a difference between versions, I'm not aware of it. To be completely honest, I'm having trouble understanding your description. Too many variables and inaccurate terminology (could be a language translation thing?). Have you confirmed that the custom add-ins actually work in 25?

Good luck.

[GaryOrrMBI]

I did this just a couple of days ago and everything worked fine.

To make sure that I was remembering which version of Revit I was in correctly I just repeated the steps and everything worked as expected: the element was copied to the clipboard from one rfa file where it had a family checkbox parameter linked to it's visibility parameter, pasted that into another family that did not have that parameter in it and the parameter was created in the second file and was tied to the visibility parameter of the pasted element.

Check to ensure that you have the latest updates perhaps? I know that there were some bugs early on. Current version is 2025.4.2

-G