Most likely the problem is that your criteria for mapping the objects is not unique enough. So, both objects match the mapping criteria you have defined so both objects are shown as mapped to the same item in your Mapped Items tree.
This happens frequently with allowing TestComplete to automatically map objects without doing any review of said objects. Two things to keep in mind when mapping objects.
1) Objects are mapped based upon who their "parent" is
2) Objects are mapped based upon the set of property/value pairs.
So, if your mapping tree has the objects having the same parent and the same property/value pairs. You'll have this conflct.
Some tips:
1) Go to Tools -> Options -> Engines -> NameMapping and turn OFF the object to use extended find whenever possible. Extended find is a good feature but, if over used, you'll end up with a parent hierarchy that is too general and you end up with this problem.
2) After recording a test, go back and look at what was mapped and make any adjustments on propery/value pairs. Look for values that change dynamically with each test run and modify those appropriately or even remove them and replace them with other properties.
3) Use more than one property/value pair to map an object. The more properties you can include to distinguish one object from another, the better. For example, in your case, it's possible that it's simply using the "class" property... two objects, same class, same parent... same mapping
Robert Martin
[Hall of Fame]Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
