Hello, My Dynamo script was working perfectly earlier today. I downloaded the Orchid package this afternoon and initially I got the following error: Warning: Multiple definitions for ‘Revit.Elements.Element’ are found as Revit.Elements.Element, Orchid.Revit.Elements.Element No property called El…

No problem, the reason for this is that the namespace for the “GetParameterValueByName” is a Revit related instance rather than a Dynamo one… This, I know, is confusing… But bear with me… The only way I’ve found to get around this is not by specifying in the code exactly the package you want to ut…

Your issue is that you have multiple methods with the same name… Nothing to do with the Orchid package … Simply add DSCore. in front of the affected pieces of code… Start with the “Element” then do the same to the “List” etc. That is the risk when mainly using code-blocks instead of nodes …

Thanks @Jonathan.Olesen . Sorry for the delayed response - it was a long weekend :slight_smile: Thanks for the link to the post about methods and names, it makes good sense. @m.rijsmus actually assisted me with DS previously and had DSCore. infront of his lines, and now I know why :). I have made ad…

Day made. I tried Autodesk.Revit. amongst others previously, but couldn’t get it resolved. Utilizing a method not available in the custom packages but only in the integrated OOTB one. Quite interesting - how on Earth did you figure that one out? Haha. It all makes sense in the end. …

[image] Connor: how on Earth did you figure that one out? I used the “Node to code” option… (Sidenote, it didn’t work in Dynamo 2.x so had to go back to 1.3.x to find the method) :slight_smile:

I’m having this same issue, having re-installed Orchid (which is excellent). Given I’ve used plenty of code blocks across our dynamo script library, I’m going to uninstall Orchid again and give up on certain functions for Dynamo. I did fire up Dynamo 1.3 and do some node to code, which works as @Jo…

Appreciate the reply, and I had looked at your example (which helps greatly with my understanding thank you!). I suppose I’m just surprised that I need to get more specific to call the OOTB functions - but I can see now the mechanics of it all. Thanks for you help!

DSCore. does not seem to work in Dynamo 2.12 (Revit 2022). Any ideas if this got changed? I had to use Autodesk.DesignScript.Geometry. [Screenshot 2022-07-13 123200]

[image] lazarica.tesu: Autodesk.DesignScript.Geometry. Nice :smiley: thanks! it works

Warning: Multiple definitions for Revit.Elements.Element found

Revit

Jonathan.Olesen April 17, 2019, 10:51am 8

The “solution”/answer to your question have to do with namespaces within the packeges you have. The best way is to always define the namespace you’re in.

It is quite well explained in this thread:

Topic		Replies	Views
How to Code without getting "Multiple Definition" Warning dynamo	11	146	February 14, 2025
How do I get the correct input Autodesk.Revit.DB.xxx VS xxx Revit	13	729	December 17, 2019
Problem with Rhythm package 2018.3.2 Packages	24	2960	September 20, 2018
Namespace DesignScript	20	2388	September 20, 2018
Orchid install multiple definitions	4	452	January 21, 2022

Warning: Multiple definitions for Revit.Elements.Element found

Related topics