Announcement

Collapse
No announcement yet.

Setting default value for yes/no Shard parameter?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Setting default value for yes/no Shard parameter?

    Hi guys,
    I created a yes/no Shared Parameter to control visibility of doors/windows in Schedule.
    Works great with my own doors and windows but with generic stuff, the parameter is turned on by default when they are loaded in a project thus making those doors/windows not appear in the schedule. Then you have to manually uncheck the parameter on those elements.

    Any way to make the shared parameter be unchecked by default?

    I guess I can always reverse the Filtering in Schedule to hide stuff when parameter is unchecked rather than checked, but at this stage there are more doors made to properly use the parameter than not.

    Any suggestions?


    Edit:
    Generic doors/windows inserted in a project are neither on or off, they are greyed out. Even if I reverse the filtering so that objects hide when unchecked. loaded non office standard doors have this parameter greyed out and still will not appear in the schedule, only when I click on greyed out parameter does it become active and then it can be turned on/off.
    Last edited by milos; February 5, 2012, 11:51 PM.

    #2
    Did you create a Project parameter?

    If you made a Shared Parameter and also put it into the OOTB content you should be able to switch to your preference, so it loads in like you want to.

    Otherwise just duplicate your schedule, uncheck Itemize every instance and change you sorting so all your content is 1 line and you can check/uncheck everything loaded into the project in 1 go.

    Comment


      #3
      Hi Bjorn_K,
      yep definitely created a Project Parameter as well. I could easily insert a shared parameter into generic content but my fear lies in people in the office downloading content from likes of RevitCity and not having their content showing up in door/window schedule. Thus creating havoc. No point in having this shared parameter if it isn't 100% effective all the time.

      I think I might go back to my old method of using a text parameter in which you would have to write "H" to hide the element. That way it makes no difference if the parameter is in the content or not.
      This is what you get when you try to fix things that ain't broken.
      If anyone has any idea why the yes/no parameter is defaulting to "yes" state in families without the parameter preloaded please let me know.

      Comment


        #4
        I believe the parameter is actually not defaulting to anything (ie: its a greyed out tick) which means its neither a yes or a no.
        Without actually seeing the filter in your schedule, cant you change it so instead of it filtering for parameter "equals" No, filter it for parameter "doesnt equal" Yes
        Alex Page
        RevitWorks Ltd
        Check out our Door Factory, the door maker add-in for Revit

        Comment


          #5
          Already tried it Alex, and as you said because it is greyed out it is neither on or off so filtering in that state doesn't work.
          I think text based parameter is more secure and will give me proper result 100% at this stage.

          Comment


            #6
            I must be missing the point, have a look at attached images, with x3 schedules and their associated filters: As you can see, the schedules as shown are correctly leaving the greyed out tickboxes in the schedule...?OnOff Filters.png

            (edit) - the image shows Family2 (which the tickbox parameter hasnt been assigned yet) shown in "filtered" schedules successfully... isn't that what you require?
            Last edited by Alex Page; February 10, 2012, 01:57 AM.
            Alex Page
            RevitWorks Ltd
            Check out our Door Factory, the door maker add-in for Revit

            Comment

            Related Topics

            Collapse

            Working...
            X