The User Interface hierarchy consists of children and parents, depending on what level of the selector you are looking at. If you ever have problems getting a good selector, you can always add more children or parents.
Let`s have a closer look and analyze the selector of the editable field inside a Notepad file.
The first row identifies the application and the actual window we are working with. In our case, the application is notepad.exe, the class is notepad and the title of the notepad file is “Untitled – Notepad”.
The next two rows identify our control in the application window hierarchy.
Some programs have a volatile layout – because of nodes with unsteady attribute values; as in the case of web-apps, but not only – which make automatic generation of reliable selectors impossible.
UiPath can’t always predict how an attribute’s value will change along the runtime, or between runs of an app, but there are workarounds for this.
For example we notice that UiPath recognizes the notepad window by its title:
title=‘Untitled - Notepad’
However, that title can change very easily because if you will open a file name have abc.txt then the selectors for this will have the title=“abc - Notepad”. The solution to this problem is to:
• build better selectors
• in our case modify the title attribute using the * wildcard:
Please always use UIexplorer to get more with selectors in your case.
This link is very useful for you i guess