I'm understanding that when a Yes/No param is added to a room (for example), the default is that the checkbox in the room's properties is gray since the value of the checkbox is null on creation.
Has anyone found a way to force a default of yes or no on these? With sometimes hundreds of rooms that are usually either 90% yes or 90% no, it's a pain to have to go click that checkbox on every room. Yes, we typically just do this in a schedule view, but still. Having a choice of default would be nice.
Thanks!
Matt
Gelöst! Gehe zur Lösung
Gelöst von TheMattatonAP. Gehe zur Lösung
Hello @TheMattatonAP
you can Use Dynamo or filter you can use it also,
but what if there is no common parameter to group of rooms, that's it the main problem
can you told me more about your project to help you.
Best regards,,
Mohamed Nassar
An example would be a parameter we use to designate if a room should be used in occupancy calculations. Non-Calculated Area - the default should be No since most rooms should be used for calculations. So, when that checkbox is added to each room we'd like it to already be cleared and just check it if we need to.
Where this becomes an issue being null is our schedule and calculated fields therein are looking for an area based on whether the area of the room is to be calculated or not. If the checkbox is null, we get no area number. We have to click the gray checkbox to clear it or check it before the calculations can happen.
I think the default is always on/yes in general? But below are some options:
1. Isolate category, select all, turn on/off
2. Adjust in schedule
3. Dynamo
No, the default looks like it's yes...checked, but grayed out. It's actually null. There is no value at all. You have to actively click it to set a value.
I think I'll go the Dynamo route to set the defaults.
Thanks!
ok i Sir i will answer you according what i understand and i can hear more from you if i miss understand any thing.
If you create a parameter in family 2D or 3D you can default the parameter inside the family not the project,
Example if i make Visible Parameter to nested Family and non-Check it in the Family Editor screen it will reflect the model also by not checked in the project and the Opposite is correct and try to make it instance parameter to have the availability to check each single room stand alone.
Right. This is specifically a shared->project param. It doesn't come from a family.
I'll just have to use Dynamo to quickly set the defaults.
Thanks!
Another thought; with a schedule you could add a calculated parameter inverting the default - not([youryesnoparameterhere]) - but since the default is null you still have to 'activate' the value anyway. But could have saved you some clicks, but you're right I'd probably try with Dynamo also...
OK that's great idea, hope to hear a good news from you.
Best Regards,,
Mohamed Nassar
For posterity...here's what I did in Dynamo. Pretty simple.
Interestingly, according to Dynamo, the default isn't null, it's a blank.
Perfect, I like it very much.
Thanks Sir, it's honor to collaborate in the future also
Best Regards,,
Mohamed Nassar
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.