No announcement yet.

Rename shared paraments - GUID causing issues?

  • Filter
  • Time
  • Show
Clear All
new posts

    Rename shared paraments - GUID causing issues?

    I'm going through our content just now, currently the families and all the parameters are set to UPPERCASE but I've been told I need to change it to CamelCase.

    I've renamed all the Shared Parameters but I can't get them to the change in the families which I believe is because of the GUID.

    For example where I originally had DUCT CONN HEIGHT I've now changed that to DuctConnectionHeight in the text file. So the name is definitely different it's not just the case that's changed.

    However if I open a family and try to change it I can't. Even if I delete the parameter completely and try to add it back in, I select DuctConnectionHeight in the list and it brings in DUCT CONN HEIGHT.

    I think that's because it's reading the GUID and recognising that it's the same parameter as before.

    Is there anyway I can update these fields? I've got around 1,200 to fix, I can't set them all up from scratch, there must be a better way.


    IMO - leave the old parameter alone and create a new one. Then you will need to use a 3rd party tool of some variety (CTC BIM Manager Suite, Spectrum, Ideate, etc) to swap your old parameter for your new parameter. I've used CTC & Spectrum and both are good. The functionality varies slightly but the basics are the same, at least as it relates to managing parameters. Either will pay for itself in no time.
    Revit for newbies - A starting point for RFO

    BEER: Better, Efficient, Elegant, Repeatable.


      The shared parameters should not be edited in the text file because that is how they are stored and you cannot work with them through that file. you either need to rename them individually or search the Autodesk app store for "shared parameter managers". These allow you to update the naming and categories while keeping the functionality in tact.


        Im with Chad: Create a new shared parameter file and then buy a shared parameter manager which can bulk change directories of families: will save you heaps of time/money.
        My preference (not that Ive tried many others) is RTVTools Shared Parameter Manager: a one year subscription is only ~US$130
        Alex Page
        RevitWorks Ltd
        Check out our Door Factory, the door maker add-in for Revit


          It's been my experience that the only time we can get away with editing the SP file directly is before you actually use that parameter definition stored in it. Once that parameter has been applied in a family or in a project you won't be able to alter the version in the project or the family with the changed version in the SP.

          Surely, you noticed...when you read the SP file, it starts with an admonishment to not edit the file directly, that's the first clue the plan isn't going to survive contact with the enemy.

          Create a separate parameter and reassign...or use a 3rd party tool to do it.


            What are Shared Parameters?

            Are they;
            A) A way for everyone to create their own 'system' parameters, each with their own method of naming things because there are too many mierenneukers who care about things like capital letters, resulting in endless growth of new parameters that do the same thing but with slightly different names that have to be exported/imported each time you work with someone new?

            B) A container for transferring a certain type of data between families, projects and tags?

            Personally I think the answer is B, which is why I use a shared parameter file that simply consists of a shared parameter for every parameter Type that it is possible to make. The shared parameters are named exactly the same as the Type of information they carry is named in Revit.

            So for any time you need a shared parameter for something new, there already is one, for every possible type of data, that will do the job. So you dont have to make a new one, with a new incompatible GUID and a new naming convention you just invented....
            If you want parameter names that are self explanatory, with a certain style, or with tooltips etc. Just make a normal parameter for the user interface/properties and link it to the shared one...
            It really doesnt matter if the same shared parameter, with the same name, is used for different things in different families or categories if it is carrying the same Type of data. So this greatly reduces the number of shared parameters needed. Lots of parameters doing the same thing with different names are just redundant crap that you need to maintain.

            Obviously there may be some cases where a specifically named custom shared parameter is better, but if everyone would just work with a basic set of core shared parameters for 99% of the uses they are needed for this whole discussion would be a thing of the past.

            Heres my core revit shared parameter file, if you like the idea then feel free to use it (Definitely dont make yet another version..)
            Attached Files
            "One must imagine Sisyphus happy." Albert Camus - "The innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may ​do well under the new." Nicolo Machiavelli -"Things that are too complex are not useful, Things that are useful are simple." Mikhail Kalashnikov


              Originally posted by josephpeel View Post
              One function of a shared parameter that you forgot to mention is that it maintains its value even when you swap families that both contain that parameter. I've got a whole bunch of those that I keep in a separate shared parameter file, because there will never be anyone who wants to use it in a tag or schedule.
              There must be a better way...

              Ekko Nap
              Professional nitpicker, architect, revit consultant, etc.


                Good point. I would consider that a good reason to add to the core parameters.
                Instance parameters also keep their value between types of the same family when switched, a reason to have fewer families that are more parametric.
                "One must imagine Sisyphus happy." Albert Camus - "The innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may ​do well under the new." Nicolo Machiavelli -"Things that are too complex are not useful, Things that are useful are simple." Mikhail Kalashnikov


                Related Topics