Sounds like there needs to be an object tree refresh somewhere in your automated test.. that after you run the search, refresh the NameMapping tree and see what happens.
Hello Tristaanogre,
Thank you for the suggestion, it is helping me come up with potential ways to get around this situation. Unfortunately it did not appear to work, as I added in a script to refresh the process tree after the test performed the search. The only way that I have been able to consistently get the objects to appear within the object browser is through running the search manually.
That being said, this exercise did uncover additional information for me that I was not previously aware of regarding this:
1. When I am able to force the objects to appear in the object browser, they have a ClassName property of (Empty). I'm not sure if this may have something to do with TestComplete's difficulty finding them, as part of the configuration for working with MSAA objects involved specifying certain classnames for the objects we would want to work with from what I recall.
2. Before I run the search, there are 29 children of the panel that holds the search results, and after the search is run there are 30. However, when comparing the lists to each other, there does not actually appear to be a new object there, even after a refresh. Am off to look up how to use the FindAllChildren method now. Hopefully that may lead me to something
