is Jeremy saying every parameter bought into the project is a shared parameter by definition?
https://thebuildingcoder.typepad.com/blog/2008/11/defining-a-new-parameter.html
New parameters can only be created as shared parameters
Which is what Erik was saying…
That’s from 2008… @Jeremy_Tammik has anything changed? 
(My guess would be No!)
Mark
Edit This is 2016… Re: Key schedule add parameter - Autodesk Community
My guess is no, too. Happy New Year!
thank you for your appreciation!
Hi Erik
It’s getting really interesting now!
What i miss is the check with shared parameter file to keep only those parameters.
I guess it can be done with OOTB nodes, but it would clarify the process for others too.
Good job!
thnx
Edit:
Do you have nodes which can give me a decisive answer whether the parameter originates from the project or a family?
Hi @erfajo
I ran this on a new project started by choosing none when it ask me for the project-template.
Can you explain?
I use Element.Name+ beacause someone made it to use a bigger scope getting names. so my initial thought was why not use the bigger scope.
Maybe @jacob.small can shed some light on what these parameters are/do, cleaning up my models i need to know what can be deleted
can’t seem to find them in here. further exploring needed, im on it, want to know @Luke_Johnson, @Jeremy_Tammik
btw @erfajo deleting a parameter by name is ok, but deleting a parameter by GUID is better i think, it will force you to know exactly what you are doing
You help a lot of people out in difficult situations.
I like it
@erfajo
I just had this thought:
What if i could make those “loose” shared parameters into Shared Project Parameters with the categories still attached (no data loss). I can them delete them and investigate further if needed. But now i have control from the UI.
