"Use extended find when possible" with "Map object names automatically" creating ambiguous mappings

[Actinomorphic]

With a particular web project I'm working on, having "Use extended find when possible" with "Map object names automatically" both enabled caused me endless grief. I had to disable "Use extended find when possible". With "Use extended find when possible", I was getting ambiguous mappings. TC kept using the extended property "idStr" as the unique identifier. The problem is that many objects had the same value associated with their "idStr" property. The extended property that was unique among the objects was "ObjectIdentifier".

Why did TC use this "idStr" extended property knowing that it was not unique? Why did it not opt for "ObjectIdentifier" knowing that it was unique? Is there a way to configure it such that it would use "ObjectIdentifier" rather than "idStr"?

[AlexKaras · Accepted solution]

Hi,

You may consider Templates (https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/temp...).

But honestly, automatic objects' mapping and extended find for all mapped objects is far not the best approach.

The most effective approach is the investigation of the tested application in the Object Browser and manual mapping of the required objects before recording. https://community.smartbear.com/t5/TestComplete-Functional-Web/Object-mapping-for-multiple-environme... for more details.