Announcement

Collapse
No announcement yet.

Shared Nested Family (Instance) Parameters not available in project?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Shared Nested Family (Instance) Parameters not available in project?

    Following THIS THREAD

    I've just encountered the scenario I'd queried (regarding to controlling shared nested families) first hand, and I'm still a little confused...

    The attached family is an experiment we've been playing with to monitor/manage our office equipment - kind of like a pseudo-FM model, where we've also been playing around with our Roombook/ADB/Codebook functionality.

    It's a (shared) "workstation" - with instance parameters for CPU, GPU, etc.... nested within it is a (shared) "software" family, with instance parameters for, er software....

    Loaded into a project, the instance parameters of the workstation family are available, but once tabbed-through, the software family isn't. Placed singularly, the parameters are.

    This isn't how I remembered shared-nesting was meant to work...

    Do I have to add, and associate, ALL those paramters to the host as well? :crazy:
    Attached Files
    Tags: None
    #2
    Yes it was, and always has been. I'm guessing you got confused with extracting the data through schedules. You can have the software family linked to the hardware family. Create a Mark-parameter in both families and nest the Software Mark in the Hardware family.
    IN your PROJECT environment you can now create schedules reading all Software parameters needed and identify those by Mark.
    Martijn de Riet
    Professional Revit Consultant | Revit API Developer
    MdR Advies
    Planta1 Revit Online Consulting

    Comment

      #3
      Type parameters are available through the Project. Instances must be tied to the Parent.
      Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
      @Web | @Twitter | @LinkedIn | @Email

      Comment

        #4
        Originally posted by Twiceroadsfool View Post
        Type parameters are available through the Project. Instances must be tied to the Parent.
        Right, sorry: missed the instance part... :hide:
        Martijn de Riet
        Professional Revit Consultant | Revit API Developer
        MdR Advies
        Planta1 Revit Online Consulting

        Comment

          #5
          Originally posted by Twiceroadsfool View Post
          Type parameters are available through the Project. Instances must be tied to the Parent.
          And that's how I always understood it - a combination of wishful thinking and that other thread was throwing me off... the guy building these is just going to push the parameters into the workstation family out right...

          Originally posted by mdradvies View Post
          Create a Mark-parameter in both families and nest the Software Mark in the Hardware family.
          IN your PROJECT environment you can now create schedules reading all Software parameters needed and identify those by Mark.
          Any particular kind of parameter? I've just added a yes/no "Test_Mark" and associated them as you suggest, but apart from being able to tick it on/off (in the workstation family) nothing else appears to happen... in either way the schedule gives me the option to list all the (uneditable) parameters, but neither way gives me control over them.

          EDIT

          Originally posted by mdradvies View Post
          Right, sorry: missed the instance part... :hide:
          Again, it's no biggy, my guy's probably rebuilt it by now... I guess I was/am just having a bit of a late-Friday afternoon "wha?" moment.

          Comment

            #6
            The only ones you cant nest at all are Family Type parameters. Sucky.
            Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
            @Web | @Twitter | @LinkedIn | @Email

            Comment

              #7
              Ok, I dove in this since I do have a family for calculating egress length which has nested instance shared parameters but it still works... Only problem: I created this a year ago and never properly documented it.

              As it turns out, you CAN use Nested Instance Parameters, in the project. Just need a workaround. I posted a blog about this, find it here. And I attached the sample family with this post.
              Attached Files
              Last edited by mdradvies; August 27, 2011, 12:51 PM. Reason: added link to blog
              Martijn de Riet
              Professional Revit Consultant | Revit API Developer
              MdR Advies
              Planta1 Revit Online Consulting

              Comment

              Previous template Next

              Related Topics

              Collapse
              Working...
              X