Project Params Created Identical, one will go in formula, the other NOT

Project Params Created Identical, one will go in formula, the other NOT

mdhutchinson
Advisor Advisor
1,003 Views
23 Replies
Message 1 of 24

Project Params Created Identical, one will go in formula, the other NOT

mdhutchinson
Advisor
Advisor

I have two project parameters I am referencing in formula intended to drive Yes/No Visibility Parameters...

Both referenced parameters have been created the same way. Additionally, the Visibility Parameters have also been created the same way... both are Yes/No grouped under Visibility. 

One (Ceiling Elevation) I can reference in the formula without error... the other (Floor Thickness) I cannot.  I've checked, rechecked and recreated the troubled parameter, but still cannot resolve the issue.

 

Can anyone give me a clue what I might look at?

2018-10-10_9-56-59.jpg

0 Likes
1,004 Views
23 Replies
Replies (23)
Message 2 of 24

cbcarch
Advisor
Advisor

Just a guess,

But perhaps it could be a "conflict" between a Project Parameter and a Shared Family Parameter ( Floors and/or Rooms?).

Cliff B. Collins
Registered Architect The Lamar Johnson Collaborative Architects-St. Louis, MO
0 Likes
Message 3 of 24

ToanDN
Consultant
Consultant
Parentheses?
0 Likes
Message 4 of 24

mdhutchinson
Advisor
Advisor

It's not the parenthesis, I tried with and/or without paren's, even < 0 or =,  or confusion between Room Ceiling Floor. This tag will be driven by Dynamo... all of the parameters have intentionally been added to the Room object.

 

I've chosen to rebuild the tag from the ground up. I'll report back. (always good to start over when you're as green as I, (learn something new the second time)

 

...meanwhile any other thoughts and/or what to look out for would be appreciated.  

0 Likes
Message 5 of 24

SteveKStafford
Mentor
Mentor

I think it is a simpler issue "Floor Thickness" isn't a parameter listed on the left...is there one? If so it should be in the list of parameters somewhere. Otherwise that message means it is spelled differently.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes
Message 6 of 24

Corsten.Au
Advisor
Advisor

Hi

 

 

In Default tags ( Floor, Window, Doors etc ), you may use

default parameters available in Revit... and there is no way to use

" Project Parameter" which are created in Revit Project independently..

there is no connection between tags and Project parameters as such..

 

Way to solve this is to use " Shared Parameter " 

 

" The error/warning clearly shows that parameter doesn't exist "

Best luck

Corsten
Building Designer
0 Likes
Message 7 of 24

barthbradley
Consultant
Consultant

Just curious to know how "Ceiling Height" is working. Is it under Identity Data?  

0 Likes
Message 8 of 24

mdhutchinson
Advisor
Advisor

I have ceiling height driven via Dynamo Graph. The graph gets the ceiling directly over the room reference point and obtains the elevation directly from that parameter.  And yes, it is grouped under identity data.for no other reason except to keep it together with the other 3 parameters in Properties Palette.  As I understand it, what it is grouped under is of no consequence in regards to behavior (or am I mistakened?)

0 Likes
Message 9 of 24

ToanDN
Consultant
Consultant
Is "Floor Thickness" under Identity Data as well?
0 Likes
Message 10 of 24

mdhutchinson
Advisor
Advisor

Yes, Floor Thickness is under identity data. I am thinking it’s value will be user supplied. I’ve not found this data available except by user research given the product/supplier and a visit to the suppliers web site... or perhaps a detail/section cut at the floor level.

0 Likes
Message 11 of 24

barthbradley
Consultant
Consultant

If Floor Thickness is under Identity Data, then it should be recognized in a formula. Try copying and pasting it's name into the formula.  

0 Likes
Message 12 of 24

ToanDN
Consultant
Consultant

Seems to work here.

 

Capture.PNG

0 Likes
Message 13 of 24

barthbradley
Consultant
Consultant

you know @mdhutchinson, if it doesn't work by the copy-paste method either, you're more than welcomed to post the family here for us to inspect.  

0 Likes
Message 14 of 24

mdhutchinson
Advisor
Advisor

... ok, I started over from the ground up... but am still having issues

 

Is your Screen Shot (Family Types dialog) taken while inside the Family Editor... ?

 

... it must be. The only way I could use the Parameter(s) in the formula was to pull the Shared Parameters into the Family as Family Parameters.  

So, I guess I accomplished what I think you did, at least inside the Family Editor... and if I edited the value while inside the Family Editor... Family Types Dialog, the Yes/No behaved accordingly,... but in the model it would not read the values actually stored in the Room object.

 

2018-10-11_13-23-28.jpg

 

0 Likes
Message 15 of 24

ToanDN
Consultant
Consultant
Yes the screenshot is taken in the family environment. You need to add the shared parameters Ceiling Height and Floor Thickness to the Rooms category in the Project.
0 Likes
Message 16 of 24

mdhutchinson
Advisor
Advisor

I think that I did.

 

2018-10-11_13-48-10.jpg

0 Likes
Message 17 of 24

ToanDN
Consultant
Consultant

If you are looking for using shared parameters of the door family to control the visibility of the tag's elements then you cannot do that.  You can only use them to drive the Labels of the tag family via calculated value formulas.  For example:

 

Calculated value label:  if (Ceiling Height = 0, " ", "some text")

0 Likes
Message 18 of 24

mdhutchinson
Advisor
Advisor

Now I am confused. What do doors have to do with it?

Your reply where you showed me.... "Seems to work here"  ...was incorrect and misleading?

 

0 Likes
Message 19 of 24

ToanDN
Consultant
Consultant

@mdhutchinson wrote:

Now I am confused. What do doors have to do with it?

Your reply where you showed me.... "Seems to work here"  ...was incorrect and misleading?

 


Sorry, not door.  But the principle is the same.  Shared parameters of host (Rooms in this case) only drive the Labels of the Tags, not the Visibility.

 

When I said "seems to work", I was only addressing the immediate question, the formula validity.  I wasn't aware of the bigger picture until reading further posts of yours.

0 Likes
Message 20 of 24

barthbradley
Consultant
Consultant

@mdhutchinson wrote:

Now I am confused.


Me too. he,he. 

 

Looks like to have the Tag figured out though. And it looks like you created Project Parameters for Rooms that use the same Shared Parameter that the Tag is using. So now your Tag can populate with the values given to the Room's Project Shared Parameters.  

 

Are the Tags not behaving the way you want them to on placement? 

 

 

BTW @mdhutchinson: you mentioned something about Dynamo at the onset of this thread.  Are you still going to be using a Dynamo to manage/manipulate all this information? I'd be curious to know the dyn routine. 

0 Likes