After installing Revit 2020, the new dynamo presented issues when searching for specific nodes. The search results were too limited and I had trouble finding what I want by typing key words. Whereas in the previous version it was much easier to find what I wanted.
I tried troubleshooting the issue by removing all packages and reinstalling them one by one, thinking it might be something related to one of the packages. But I found out it had nothing to do with any package.
Then I found this topic
which informed that this issue was due to a change by design.
So my question is, what is the new search strategy? How should we search for nodes if they don’t come up when typing key words?
Hi @sed07 I have the same issue, my workaround at the moment is to try to type the node as it is. I mean if a node is called Element.GetParameterValueByName and you search for “element get parameter…” it will not show any results that’s unfortunate, so in order to show results in the search you need to type exactly the name of the node you’re looking for…
Please check the images below. And of course if anyone else found a solution to that please share!!
Thanks for the reply. It’s unfortunate that we have to resort to such inconvenient workarounds, as the search function is supposed to help us find nodes, not force us to remember all of their exact names.
I’m baffled how such a crucial element of dynamo was changed so suddenly and without (sufficient) testing, or even having it as an option or setting that can be turned off and on. And I’m surprised more people are not complaining about it, as it really impedes the workflow having to spend so much time to find nodes you want to work with.
If anyone is reading this and experiencing the same problem, please reply so that we know to what extent this is affecting people.
yes you’re right @sed07, I totally agree. You could also try to open Dynamo 1.3x and search for the node, then copy paste the exact name… it’s not the most beautiful solution but it works, at least until they fix this (hope they do soon)
It seems that including spaces in your search is equivalent to separate search keys and that’s why you get so many returns. Keep in mind that the (searchable) node name doesn’t include Class and therefore including it in your search is actually counter-productive. The full name is great for when you know exactly what you’re looking for but otherwise using spaces can return too many results. When I can’t remember the full name of a node I usually search for the part I remember with no spaces as this should find an exact match.
With all of that said, it’s still a pain to search for something.
I also wanted to include that I have not had a chance to test the search in Revit 2020 + Dynamo 2.1.0. However, I was among the users that felt that the search needed serious improvements since Dynamo 2.0.0 rolled out.
You’re right, there were issues with it before that I’ve experienced myself as well, namely the slow nature and lag. It seems like they have fixed it, but at the expense of seriously limiting the search results and making them less likely to turn up what you type (unless you type the exact node name).
Also your case is probably the reason why few people have experienced this issue (maybe not so many people have switched to the new revit and dynamo yet).
I will consider opening a github issue soon, following your suggestion.
Same issues here. If I search ‘pararmeter’ in dynamo 1.3 i can find the node element.parameter. If I search ‘parameter’ ,no spaces, in dynamo 2.2 it returns almost nothing but if i search element.parameter it is there.
There were changes made to Search in Dynamo 2.1 to improve accuracy and performance that unfortunately came at a tradeoff with discoverability. We’re looking into doing another pass at Search to raise the bar again on keyword relevancy.
Search is now much faster and much more accurate with the results returned - but means you have to be more accurate in typing to achieve said results. Historically the more packages you had, the slower search became to a point where it was untenable with thousands of exposed nodes (Not atypical for a user to have).
We fully realise that the current solution isn’t perfect - hence the next pass on this - but do believe in the short term that this is a better solution that we had before
Thank you solamour, indeed in the previous versions the search could be frustrating because of the return delay. However, and I’m talking here as an almost newbie, it was very helpful to have a lot of results when you were not exactly sure about what you were looking for. It helped me many times discover nodes that could resolve a problem. Not to mention that I don’t remember most of the exact node names. I guess it would be useful to have the option to switch between many results/slow and few results/fast.
Until things are not changed I’d better stick with a previous version, is it possible to downgrade?