Create project parameter not shared

Hi guys,

I want to create project parameters using dynamo but I need the parameters to be part of a key schedule so they cannot be shared parameters.

I have found two nodes one built-in and one from the orchid package.

They both say that they create document parameters but when I check the parameters they are identified as shared.

What am I missing here, is this simple thing not possible to achieve…

I have found similar threads talking about it but I cannot believe this is not possible to do.

Any ideas…

Revit will only allow programmatically creating parameters from an external definition, not an internal one. This means that unless there is a user action, all parameters are shared parameters which means no key schedule parameters. This has been the case for awhile now, and as far as I know continues to be this way.

You may be able to create what you need though other methods though. Look into the key schedule nodes in the Archi-lab package.

Thanks Jacob for looking into this.

The Archi-lab node helps feed data in a key schedule that already have the parameters so nothing really.

We are stuck with both facts Revit does not allow to programmaticaly create project parameters and Key schedules dont allow to use share parameters!!!

Ah, shucks - thought Lonrad May have had some black magic. Least it is a one time thing to create (you can transfer the key schedule view next time which brings the parameters with it).

Also, it won’t help today (or this Revit release) but check the roadmaps for this year as there is a relevant topic in there for you. Revit Public Roadmap Update - April 2020 - Revit

Fingers cross, hopefully we can see this functionality included in the next update!!!

via GIPHY

2 Likes

Has this issue being addressed in more recent Dynamos?

I am using the “Parameter.CreateProjectParameter” node and I cannot make anything but shared parameters…

Thank you

The Revit API only allows creation of shared parameters at this time.

if you are asking about keyschedule as orginal poster is in revit 2023 you can use shared parameter in key schedule though.

Ugh, I need a non shared parameter too.

Why?

Not asking to be a jerk, but genuinely curious as the benefits of project parameters are significantly less and on one has given a compelling reason for programmatic project parameter creation.

Follow-up question just cause I’m curious and want to understand.
When the current node makes a “project parameter” (shared parameter) does it write a shared parameter text file and store it somewhere? Or does it write it and delete it?

One of the disadvantages of Shared Parameters is that they cannot be purged from a project unless you use Guardian. You can delete the parameter from Project Parameters and you’ll think its gone but its not.
Maybe I’m just being picky, its not consequential to anything (that I’ve noticed yet) just annoying that they don’t purge.

How you purge matters, but yes they are intentionally harder to get rid of.

Write and delete. Code is here (note the ‘obsolete’ tag): DynamoRevit/src/Libraries/RevitNodes/Elements/Parameter.cs at b1636ad6eded9c968d7034bc28b2e86a18568a2a · DynamoDS/DynamoRevit · GitHub

I think I might have a workaround for a project parameter of it is really needed. Note that it will be slow as hell though and will apply to ALL categories unless someone wants to spend a LOT of time making 200+ reference files and 50+ reference files on each annual release… I know I don’t, as the benefit (easier to delete and thereby lose associated data) isn’t worth it.

1 Like

Thank you for the explanation. Since it deletes it then there’s no impact to file space, so that’s good.

Thank you for looking into it but if its really slow then don’t bother.
That reminds me of a situation I’m currently dealing with. I made a Lateral Tee duct family that populates when 2 ducts are modeled into each other at any angle. There’s over 200 parameters with formulas in the family so any time you click on it, Revit re-calcaluates the formulas. I thought it was special when I made it. Turns out the MEP team only need 45 or 30 degree tees. So even though its a solution for all cases, its a problem for modeling speed.

1 Like

Speed I am not sure about - the pace of execution might be fine. It’s the prep work that would be the issue. So many files needed…:sweat_smile:

1 Like