It would be more helpful to see what other properties TestComplete exposes to use. It could be that what you're seeing as "name" is showing up somewhere else.
As for conditional mapping... why not? It seems like that would be an optimal way to go. Although, potentially, you could get an error about a property not being supported or something.
If you can provide screenshots of properties on the object, perhaps we can help find something that would work better.
I looked again. As I was taking the requested screen shots, I saw attributes.name.nodevalue seems to work. The conditional mapping was not going to work from the TC UI because of limitations to the UI for selecting the property.
Hi,
> attributes.name.nodevalue seems to work.
This is probably the best way to go (https://support.smartbear.com/testcomplete/docs/app-testing/web/general/object-identification/using-custom-attributes.html) considering the technology your tested application is based on and obvious absence (or complete ignorance) of QA (not testing) activities. (Which is not your fault.)
Can you explain this
"considering the technology your tested application is based on and obvious absence (or complete ignorance) of QA (not testing) activities. (Which is not your fault.)"
