Announcement

Collapse
No announcement yet.

Push parameters in the project environment

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

    Push parameters in the project environment

    So, in this thread I encountered an intruiging option with schedules that I never noticed before.
    After some testing this option blew my mind: it's the holy grail for scheduling if you ever work for architects with lousy Family Management!!!

    Every contracter (or anyone else working for third parties) encounters this once in a while: you are provided with a model, and asked to do some scheduling for Quantity Takeoff or Coordination purposes. And the misery starts here...

    When you create the first (window) schedule you'll notice a whole bunch of width parameters, all referencing the total width of different windows (fig 1)
    After creating the schedule you figure: let's create a "scheduled width" parameter which adds up all those separate width parameters. This way you can clean up your schedule (fig 2). Only to find that it won't calculate. In this case, the family "ontwerpraam doesn't have the parameter "breedte_vo" so in the schedule it returns no value. Therefor, the total cannot be calculated (fig 3).

    In comes a very need trick:
    Open the schedule properties, go to the Fields Tab, select the parameter causing problems and click Edit.
    In the Parameter Properties, check the checkbox "Add to all elements in the selected category", select the category "windows" and choose whether it should be an Instance or Type Parameter (fig 4).
    The parameter is now accessible in the schedules, even with the families it's not actually in. You can now fill in a value and the Scheduled Width parameter will calculate properly (fig 5). It will even show up in the family's properties (fig 6).
    Be adviced though:

    1. This has NO relationship to the actual family. It's a dumb number. It doesn't exist in the actual Family (to test it, you can open the family in the family editor, it won't show there). So keep this to 0, only as a way to be able to create proper schedules.
    2. The choice for Instance/Type CANNOT be changed afterwards!!! In this case, I thought it would be better to make it Type instead of instance, but it cannot be accessed again (fig 6)

    But hey: there's finally a way to clean up those messy schedules!! (fig 7)
    Attached Files
    Martijn de Riet
    Professional Revit Consultant | Revit API Developer
    MdR Advies
    Planta1 Revit Online Consulting

    #2
    Aaah, I see now... that's what that option was created for! Thanks for sharing! :thumbsup:
    Freelance BIM Provider at Autodesk Services Marketplace | Linkedin

    Comment


      #3
      Bee-ee-a-u-tif-ull
      -Alex Cunningham

      Comment


        #4
        so cool man

        Comment


          #5
          Originally posted by Alfredo Medina View Post
          Aaah, I see now... that's what that option was created for! Thanks for sharing! :thumbsup:
          What I don't know: has this option always been here? If so, lie to me and say it wasn't... Cause this trick would have saved me soooo much time and :banghead: in the past. I've done some implementations with contractors where they would get an architects model.
          In Holland, it's common use amongst a lot of architects to just get their families from any place they can find them. So you have windows from different resources, all with their own parameters and workflow. After finishing their model, they put it on the contractor's plate to sort it out. How many hours I've spent opening families, applying correct parameters and reloading them, only to find that I've somehow magically screwed up the entire family, that some guy found somewhere on the internet.
          Just to get a simple window or door schedule!
          Martijn de Riet
          Professional Revit Consultant | Revit API Developer
          MdR Advies
          Planta1 Revit Online Consulting

          Comment


            #6
            another hidden gold being found!

            but looks like this option ("Add to all elements in the selected category") is always checked and greyed out in RME 2011 + 2012 no matter you use project or shared parameter, is it enabled in RAC? i mean user can (un)check it?

            Comment


              #7
              Originally posted by Ning Zhou View Post
              another hidden gold being found!

              but looks like this option ("Add to all elements in the selected category") is always checked and greyed out in RME 2011 + 2012 no matter you use project or shared parameter, is it enabled in RAC? i mean user can (un)check it?
              In which kind of family are you trying this? Doesn't work in System Families, nor when all families already have the parameter. Open the attached file in RMEP 2012 and it will work (I created it there so it's available)
              Attached Files
              Martijn de Riet
              Professional Revit Consultant | Revit API Developer
              MdR Advies
              Planta1 Revit Online Consulting

              Comment


                #8
                now ic what you mean, thanks Martijn.

                Comment

                Related Topics

                Collapse

                Working...
                X