HowTo Grey out parameter without formula

[ReneBogersREBO]

Hi all,

I have a family with 5 types in it.

Each type is a different size (I have my reasons to do it this way instead of 1 type with lookuptable).

I have a parameter "diam_01" that contains the diameter per type.

I want to extract data out of LookUpTable with this parameter to fill my other parameters for each type.

How can I grey out my parameter "diam_01" that contains the size? (I don't want users ajust this parameter for another size. Other size needs other FT).

Adding a formula doesn't do the trick, cause parameter has other value with each type.

Hope I made myself clear.

[ReneBogersREBO]

Hi all,

I have a family with 5 types in it.

Each type is a different size (I have my reasons to do it this way instead of 1 type with lookuptable).

I have a parameter "diam_01" that contains the diameter per type.

I want to extract data out of LookUpTable with this parameter to fill my other parameters for each type.

How can I grey out my parameter "diam_01" that contains the size? (I don't want users ajust this parameter for another size. Other size needs other FT).

Adding a formula doesn't do the trick, cause parameter has other value with each type.

Hope I made myself clear.

[barthbradley]

if(1=1, diam_01, diam_01) 

I think I misunderstood. What you're saying is that diam_01 is a user-entry parameter; right? And, that that entry is pulled from the Lookup table; right?  If so, it's really not possible. You could feed it with a value from another like parameter that was named "Don't Mess With Me".  Only half-kidding.  

[barthbradley]

if(1=1, diam_01, diam_01) 

I think I misunderstood. What you're saying is that diam_01 is a user-entry parameter; right? And, that that entry is pulled from the Lookup table; right?  If so, it's really not possible. You could feed it with a value from another like parameter that was named "Don't Mess With Me".  Only half-kidding.  

[L.Maas · Accepted solution]

For me it is always communicate with your users. Explain what they are (not) allowed to do.

There is another trick you could employ, create a hidden shared parameter. This parameter will be visible in the family editor but will not be visible in the project.

In the family editor

In the project

You can do this by creating a new shared parameter, then open the shared parameter txt file and manually change the VISIBLE value from 1 to 0

Make sure to make backups before doing this. As this is not common Revit procedure consider it well before applying this to your workflow. Might confuse modellers when not aware of this trick.

As mentioned communication should be your first route to follow

[L.Maas · Accepted solution]

For me it is always communicate with your users. Explain what they are (not) allowed to do.

There is another trick you could employ, create a hidden shared parameter. This parameter will be visible in the family editor but will not be visible in the project.

In the family editor

In the project

You can do this by creating a new shared parameter, then open the shared parameter txt file and manually change the VISIBLE value from 1 to 0

Make sure to make backups before doing this. As this is not common Revit procedure consider it well before applying this to your workflow. Might confuse modellers when not aware of this trick.

As mentioned communication should be your first route to follow

[ReneBogersREBO]

diam_01 is NOT a user-entry parameter, this parameter has to be pre-filled with each type, and this parameter needs to be used to extract data out of LookUpTable.

But cause of not possible to grey it out, it can be changed by the users (which results in wrong parameters for the type).

[ReneBogersREBO]

diam_01 is NOT a user-entry parameter, this parameter has to be pre-filled with each type, and this parameter needs to be used to extract data out of LookUpTable.

But cause of not possible to grey it out, it can be changed by the users (which results in wrong parameters for the type).

[ReneBogersREBO]

---

@L.Maas wrote:

For me it is always communicate with your users. Explain what they are (not) allowed to do.

---

 That's very true, but I know from experience that a lot of people (even modelers) don't listen very well all the time, and easily do things (for example ajust parameter) to make things look good (quick and dirty).

I am very fond on to try to block as much as possible, cause the info from the model needs to be as supposed it is, cause it's going to be used in other programs lateron (making orders for the mechanics and maintenance schedules)

I think the part about the hidden parameter is exactly what I need 🙂

[ReneBogersREBO]

---

@L.Maas wrote:

For me it is always communicate with your users. Explain what they are (not) allowed to do.

---

 That's very true, but I know from experience that a lot of people (even modelers) don't listen very well all the time, and easily do things (for example ajust parameter) to make things look good (quick and dirty).

I am very fond on to try to block as much as possible, cause the info from the model needs to be as supposed it is, cause it's going to be used in other programs lateron (making orders for the mechanics and maintenance schedules)

I think the part about the hidden parameter is exactly what I need 🙂