Forum Discussion
What you need to do then is work with your NameMapping and make sure that the objects are identified uniquely. Basically, what's happening is that your mapping is not specific enough... that there are two components on screen that match your mapping. You will need to correct this. This will take time. Look at ALL properties of the components.
ALSO... NameMapping works from the hierarchy as well... so, if there are two different components, they must have different parent objects. It's possible that you have Extended Find turned on for your component which is why it's finding both items as the same mapped item.
The same is the case for your FindChild... you are not being unique enough in the criteria you are using for finding the child object. You may need to start with a different parent, or add additional property/value pairs... or both.
BUT... the root cause of the problem, as you determined, is that your methods for finding the component are not specific enough to uniquely identify it. Fix that... and your problem goes away.
I had mapped them uniquely but now the issue I am facing is that the element is coming behind the transparent footer panel and when curser clicks on it, it clicks on panel rather than clicking on the element.
- tristaanogre7 years agoEsteemed Contributor
Then you need to scroll the element so that it scrolls to the top of the page... Make sure that scrollIntoView has the "true" parameter... and I would actually put that on the modal itself, not just the drop down control.