Updating Project Parameters best practice

1

Now i am working on developing a model LOI so my task is to bring all shared parameters from txt file into RVT (and this is piece of cake) then to create project parameters from them foe all model categories and finally updating all parameters values and import them back to Revit
all i could do as per attached to create project parameters for all categories however i am facing a problem in groups like in photos i couldn’t separate them according to txt file.

Creating Project Parameters from Shared file_2025-07-12_11-48-07
Creating Project Parameters from Shared file_2025-07-12_11-48-073252×914 152 KB

Screenshot 2025-07-12 115821
Screenshot 2025-07-12 115821860×993 186 KB

2

a quick no brainer is to bind them separately. two parameter lists & two group types. or run → freeze → run.

3

i recommend you think this over a bit.

Your current process:

  1. Create the shared parameters in the shared parameters document.
  2. Read the shared parameters document into Dynamo.
  3. Create a new shared parameter in the project based on the name and group name in the shared parameters file.

Since it is a new shared parameter you wind up with a different GUID than was used in the shared parameter file. Everything will look fine, but these will not be the same parameter.

Now let’s imagine you want to review the total project, so after adding all the parameters to models A, B, and C you you link model A and model B into model C. Next you go to set up a schedule that shows your parameters across all links so you can validate the completeness without having to open all three models. Sounds good, right? Except as this node creates a new shared parameter in the project you have three of each parameter to choose from. This is just like having 201726 “color” parameters in a project… never a fun thing to deal with.

Or instead imagine you want to set up a tag so you can see the schedule values in the model views? Sadly you will need to set up a different tag for each model using a different shared parameter that you will have to hack out of the model…

So overall I doubt this is really what you want… Personally I go a different route.

Instead start a new project using NONE as the template (nothing not needed will be in the file), manually add your parameters to all categories from the shared parameter file to this project, and then set up a single schedule view with ALL of the new parameters in it, and delete every other view. The resulting file should have minimal file size and work cleanly. Your prep work is done.

Now the automation bit. Write a graph which inserts that schedule view from the provided path into the project. All those juicy parameters will have transferred to the project AND you have your schedule view in the project so you can review things right away instead of having to build another graph that does the scheduling.

But if you really want (or in some cases need) to add the shared parameter from the SP file, this can be done without too much work, but I do not know of a node for it (been a few years since I have had to do this using something other than C#). Check Rhythm, Crumple, GeniusLoci, Archi-Lab, and Clockwork to start with. If not that there might be some Python which will do the trick on the forum. And if not that, maybe I can provide something for a near term fix next week.

1 Like