Usually a sign of a Revit add-in causing a conflict. Disable All Revit add-ins and see if the issues persists. If not, you know one of them is the culprit and you can start re-enabling them one at a time unitl the issue repeats and then you know which add-in needs to be updated.
If the issue does persist:
Shut down Revit
Ensure that all add-ins are disabled
Open a project with a link in it
Place the offending node, and select something
Confirm the issue persists
Upload your Revit journal and dynamo log from that session for review
Revit journal is in C:\Users\USERNAME\AppData\Local\Autodesk\Revit\Autodesk Revit 20XX\Journals\ where USERNAME is your windows username, and XX is your Revit release.
Dynamo log is in C:\Users\USERNAME\AppData\Roaming\Dynamo\Dynamo Revit\X.YY\Logs\ where USERNAME is your windows username, and X.YY is your Dynamo version.
Update: The node is working correctly when I am trying it out in one of the sample projects in Revit. I am able to select an elemt in the linked model, and the node returns the element correctly. When I then saves the .dyn script (containing only the “Select element from link” node) and reopen it, the “Element” and “Transform” -connectors are duplicated as shown in the origian post, and the node doesn’t work anymore.
The node doesn’t work within the current project thogh. When I am trying to select an elemnt within a link, the node gives me the message:
“Warning: ElementSelection.InLinkDoc operation failed. Object reference not set to an instance of an object.”
Unfortnunately I am not able to share any log-files or similair, since I got this problem in a project running in a closed network environment with classified docuemtns/files (including the revitmodel). So exporting logfiles from the “inside” to the “real world” is a cumbersome process…
I imported the packages to the inside. I will double check the version of the packages, as sudgested from @john_pierson, but i am quite sure I got the correct version.
@jacob.small I will give it a try to check the Add-ins in Revit. WIll try to Disable them and see what happens.
Update: When I load (link) my main Revit modell in to the Revit sample model, the node works. Not the other way around though (loading the Revit sample model in to my main revit model). I am getting more and more confused…
@john_pierson , would the version marked in the picture of the previous post be the correct ones to go for?
Nope, We don’t…
Though we do have a lot of linked models (~10). I did a test with only one link in it, still didn’t work…
Throwing out some “thinking out loud” questions:
Could the file size of the model cause any problems? The main models are around 500-700mb.
Could the file path between the main model and the linked model affect the node/script?
Could the model file namne affect the node/script (We don’t have any “strange” characters)?
Started thinking in the above questions after trying to load the main model into the sample project, and the node worked. While doing it the other way around, linking the sample project in to the main model caused the node to fail…
If I remeber correct, I think I did get it to work decently with the spring node version.
But we changed the work-process and managed to work within the same model (not using links).