Shared Parameter Conflict and Family Load Failure in Revit 2025

[czZZJZU]

Hi everyone,

I'm encountering an issue while trying to load a custom window family into my project in Revit 2025, and I’d appreciate any help.

Problem Summary

When attempting to load the family Roof-Windows_VELUX_GGL_electric_wall_switch into my project file 039.006_K01_F02_N01.rvt, I receive two main errors:

1. Could Not Load Family
   I get a message saying:
   “The family 'Roof-Windows_VELUX_GGL_electric_wall_switch' could not be loaded into '039.006_K01_F02_N01.rvt'. Resolve issues in the family and reload if needed.”

2. Shared Parameter Conflicts
   Revit displays the following error when trying to insert shared parameters (see attached screenshot):

   • A conflict with the existing parameter VentilationArea of type Text vs. the new one of type Area.

   • A second conflict with ThermalTransmittance of type Text vs. new one of type Number.

What I’ve Tried

• I checked the Family Types dialog in the Family Editor (see third screenshot).

• The shared parameters are correctly defined in the family as Shared, with matching data types and names.

• The parameter definitions are consistent with what is needed across other families and schedules.

What I Suspect

It seems that the project already contains parameters with the same names, but with different data types. This is causing a conflict that prevents the family from being loaded.

My Questions

1. Is there a way to force Revit to overwrite or reconcile conflicting shared parameters during family load?

2. Would renaming the parameter in the family solve the issue — or would it break tags/schedules relying on it?

3. Is there a recommended workflow to avoid these shared parameter type conflicts in collaborative environments?

Thanks in advance for any advice or similar experiences.

[azad.Nanva]

1-No, Revit does not provide a native option to automatically overwrite or reconcile shared parameter conflicts during family load.
2- Yes, it should solve the problem, but it will cause problems with tags, schedule, etc.

3-If you mean parameters with the same name, you can include the parameter type or its dependent element in the parameter name.
VentilationArea_Text
VentilationArea_Area