Forum Discussion
I'm not sure how to get it back. My guess is that there is probably a reason. In looking at the property in Object Browser, the Parent property is an object, not a string or integer.
Is there a reason why you need to use the Parent property? If you map the objects properly, the "parent" is already implied in the NameMapping hierarchy of objects. If there's a particular problem you're trying to overcome with using that property, perhaps we can help with some alternatives.
- DodongAmaw6 years agoNew Contributor
I use the parent property to access parent objects and then use their property. This to make sure I use the right object (which is not unique with the exception of a certain parent object).
If this is no longer available in 12.60 then I'd probably have to downgrade. And I am not inclined to use scripts since all my tests are keywordtests.- tristaanogre6 years agoEsteemed Contributor
The parent property IS available for use in the tests. You don't need to add the parent property to your mapping to use the parent within the automation itself.
Additionally, if you map the parent object itself and then put the child object as a descendent in the mapping tree, it will ensure that you're always getting the proper child object.
So... no need to downgrade, just better usage of the objects and namemapping feature.
- DodongAmaw6 years agoNew Contributor
I mostly use that. But our WPF appication already have a humongous object tree. Even by using extended find, the namemapping are pretty long (the longer it is the more difficult it is to read). So sometimes I use Parent property just for a specific object.
Too bad Parent object is now gone. It was a nifty thing to use without breaking the namemapping.
Thanks anyhow.
Related Content
- 9 months agoRichardPla