Hi Lucien,
| To our knowledge, the TestComplete wants to find the "table" object, but as can be seen from Object Browser, it finds two Table, one is dataPaginagor, other is tableDatabases, both of them refers to the same MappedName. That might explains why TestComplete can't distinguish which is which. Please correct me if i'm wrong here, :) |
Yes. This is exactly the case of ambiguous recognition - there are several objects that match the mapping criteria, and TestComplete cannot automatically choose which one of them to use. To resolve the issue, we need to adjust the mapping criteria so that they would provide unique identification of the object.
In most cases, we just need to add some more properties to be used for object recognition. To determine which of the properties can serve for this purpose, we need to compare the ambiguous objects in the Object Browser, compare their property values and pinpoint dissimilar values. For instance, in your case, the "touchstone" properties are idStr or ObjectIdentifier, since their values allow TestComplete to determine whether it deals with dataPaginator or tableDatabases. Once the "touchstone" property is determined, we can add it to the mapping criteria via the
Edit Name Mapping Item Dialog.
Thus, in most cases, there is no need to "rename" any objects.
Regards.
