Help with parameter erros - Revit 2023

[george8KQW4]

I was wondering if someone could help me. When I try to load this family into revit it comes up with the error message seen in the first image. 

However, when I go into the family parameter editor it comes up with the error message shown in the second image. Could anyone tell me what formula I need to use? I have attached the revit family in case anyone needs more information. 

@george8KQW4 Your post title was modified to add the product name and version and moved to the Revit forum to increase findability - CGBenner

[Ryan_GormanKT36T]

There is a lot of context that I'm missing to give you a correct answer/solution.

But let's start with, are you actually using the "TempRange" parameter?

NOTE: this test could cause other problems. I'm not suggesting it as a solution, just a test. 

Probably best to do the following NOT in the live project, but off to the side.

Try deleting that parameter from the family. Then see if family will load into the project?

[GaryOrrMBI]

The first error explains itself pretty well.

Your project file has a shared parameter with a given GUID and name, with a definition that is defined as a number. The family has a Shared Parameter with the same GUID and name that is defined as a text parameter.

The name is actually irrelevant, but them having the same GUID, but with different definitions as to parameter type creates a conflict in Revit.

For this to have happened someone almost assuredly directly edited the Shared Parameter file in a text editor and manually changed the data type from a number to text (or vice versa) between importing it into the project file (or a family already in the project) and importing it into the new family that you are trying to import into the project. A new shared parameter will need to be created for the incoming family or the conflicting parameter definition will need to be removed from the project file (which may turn out to be problematic to do depending on how it got into the project in the first place).

The second error will always occur when you attempt to type a value into a parameter field that is incompatible with that parameter type (attempting to type 6'-3" or 16CFM into a number field, for example). Simple typos can also cause this, such as doubling up on a control character like this: 6'-3""

-G