Announcement

Collapse
No announcement yet.

family and shared parameters

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

    family and shared parameters

    Hi,

    I need some ideas about a problem I have.
    I have a family in a project (special equipment), and working on this, I thought about adding shared parameters to this type of component. I did.
    Now I thought about an enhancement for my family and wanted to link a visibility (yes/no) parameter to the shared parameters I've created from the project. It works fine.
    BUT the problem is that loading the updated family in my project, ALL inputs for shared parameters are going back to default (family default)!! (I've tried the 2 options that splash on the screen) :banghead:

    I know this could have been better to have those SP from the start in my family, but the more you deal with something, the more you enhance it, no?

    Is there something I can do to work around this?

    thanks,
    Julien
    "Au royaume des aveugles, les borgnes sont mal vus!"
    P. DAC
    Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

    #2
    Changing anythign in the Family to Shared will reset all of its values in the project. The only workaround i know is to temporarily set the SP equal to a non shared parameter in the Family. (Thats the trick i use if i get content that has UNshared parameters, and i dont want to reset the values).

    But, if you put the SP in the Project, i dont know of a way around that. But hopefully someone else will chime in...

    FYI: The only parameters i add in the project itself are things that go to System Families, or things that pertain to the model (like Location or Zone).
    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


      #3
      FYI: The only parameters i add in the project itself are things that go to System Families, or things that pertain to the model (like Location or Zone).
      Thanks Aaron, the next time I'll be aware of that.
      I will keep my updated family for my next work.
      In fact, the SP I've added was first applied to walls.
      My thought was: I want to make a smart family that reads the SP applied to walls, so I've added it to my family.
      The only workaround i know is to temporarily set the SP equal to a non shared parameter in the Family.
      Do you mind adding a short explanation?
      Julien
      "Au royaume des aveugles, les borgnes sont mal vus!"
      P. DAC
      Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

      Comment


        #4
        I have actually been doing something similar just today, somone grabbed a detail component family from an older project prior to it being driven by shared parameters (which are now there for tagging)

        In this case I did what Aaron suggested, and added the shared parameter but just linked it to the current parameter in use in the family, this works fine, but you would be best to rename the family to be unique to avoid someone later reloading the new family from another project or from the library

        But after reading this I tested another level of this workflow, if I add the shared parameter to the old family, link the two with a formula as per the workflow above. I can then load the new family into the project with a different name (or rename the old one in the project), I then switch types for the instance of the old family to the new family which is loaded the shared paramter value sticks because it is present in both

        In my project though I have the additional problem if instance values (not shared) which drive the geometry of the family which then reset when I change the family. But if you just need to update shared parameters this workflow may work :beer::beer:
        Revit BLOGGAGE

        http://www.revic.org.au

        Comment


          #5
          thanks a lot, I'll give a try and let you know.
          Julien
          "Au royaume des aveugles, les borgnes sont mal vus!"
          P. DAC
          Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

          Comment


            #6
            But after reading this I tested another level of this workflow, if I add the shared parameter to the old family, link the two with a formula as per the workflow above. I can then load the new family into the project with a different name (or rename the old one in the project), I then switch types for the instance of the old family to the new family which is loaded the shared paramter value sticks because it is present in both
            So I've tried this, but it didn't work for me. I can't waist to much time with this, but the fact is that according to the category (text, length, number etc...) of the SP, I've noticed that the behavior of the input is not the same when you reload the family; sometimes the input remains (text for example), sometimes is goes away (length).

            The thing I will keep from this: always put SP in the families, except for system families.

            thanks for your time, guys.:thumbsup:
            Julien
            "Au royaume des aveugles, les borgnes sont mal vus!"
            P. DAC
            Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

            Comment

            Related Topics

            Collapse

            Working...
            X