Problem in control matching while running the automation
I am trying to interact with the web application and even I am using the appropriate matching rules and highlight option to add the control, but while I try to run the automation it gives control not matching error and I have tried using IsCreated and WaitForCreat options along with the control, in that case It will remain in idle state foreever even after control is been rendered on the browser screen.
Kindly let me know if someone is facing the same issue or else if it depends on some browser settings.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
The controller is a simple text box and the match rule I am using is List web controls, I am highlighting the text box by using the filter <input type=text> and It remains in idle state foreever if I use IsCreated or WaitForCreate, even aster control is rendered on the browser.
The exception you are receiving just indicates that you are attempting to use a control that has not been created (matched). Matching happens at more than one level - controls higher in the heirarchy have to match for the controls beneath them to match , so you should look at all of your match rules. Start at the page level and work your way down to the textbox. Remember, match rules must uniquely match the control to ensure that you match the correct control. Also, you need to wait on the last control created in the hierarchy for the best results. This usually requires a WaitForCreate on the page before you can operate on the controls on the page.
Can you share a screenshot of your page heirarchy?