Using one text Parameter to drive another doesn't work

[Anonymous]

I use the name of the first parameter in the formula column to drive the value of a second parameter.

In the project the second parameter is grayed out (because it is being driven by a formula) which as expected.

But when I change the value of the first parameter it doesn't change the second parameter!

Both are text parameters. I've tested with Shared parameters, inbuilt parameters and family parameters.

Length parameters work fine. In fact you can change either parameter and both change.

I did notice than when editing the family if I put the first parameter in the formula column, then hit apply, it disappeared. If I put a value in the first parameter it didn't disappear, even after I delete that value.

Am I right in thinking that Revit is incapable of sharing values between text parameters?

[L.Maas]

Correct. Working with string formulas is basically non existent in Revit (on many peoples wishlist).

This means you have to look for workarounds to get what you want.

In your case making several door types seems to be the easiest. Make a door type with a sliding door and door type with pivot door.

You then can preload the data in the parameter fields, meaning no formulas are necessary.

Other, more elaborate ways, could by making usie of the API or using Dynamo,

[Anonymous]

Actually I was trying to comply with a requirement in the UK NBS BIM Object Standard.

"2.3.5 The BIM object shall map hard coded properties that do not conform to naming conventions in section 5 ‘Metadata Requirements’
to a correctly spelt property based upon the order of selection in clause 2.3.3, e.g. ‘Fire Rating’ (hard coded) should be mapped to
the IFC property ‘FireRating’."

Looks like you can't do it in Revit. I wonder if they know.

[L.Maas]

I am not familiar with that standard.

If you create a door family with several types. Than to each door type you can assign the proper IFC classifications.

In extreme cases you might have to create several families.

Would that not solve your standards porblem?

[Keith_Wilkinson]

I think I must be reading this differently from you Ant.  I read it that your IFC Parameter should be set to equal the value of the hard coded parameter.  In this example they are saying that the hard coded parameter "Fire Rating" drives the IFC parameter "FireRating" which Revit will do fine... 

Its the name of the parameter it's referring to being named correctly not the actual value of the parameter.

I must confess I've not really done terribly much with IFC parameters but that is certainly my reading of it this clause.

[Anonymous]

Keith, what you are showing doesn't actually work in Revit. Have a look at the screen grab I uploaded with this post.

It SHOULD work, but AutoDesk don't support text format parameters in formulas.

[Anonymous]

Yes Enlint, solve the problem but introduce an ENORMOUS amount of extra work and potential errors.

We're talking here about multiple parameters that mean the same thing but are not connected.

Not very BIM like.

[Keith_Wilkinson]

hmm... I see watt our saying, I'll need to look at this again when I get into the office.

[Keith_Wilkinson]

This is very odd IMO. I see exactly what you are saying.

In the family editor the parameters work as expected but in the project they don't - as you point out they fail to update. Whilst I can understand not being able to use text values in a formula not being able to make one parameter equal to another does seem a bit nuts.

I don't think the workaround proposed is, well, workable...