You get that warning when Ranorex is able to find a repository item using its absolute path, but it wasn't able to find the item using relative paths with respect to the folder the item is in. That means, that the path for a parent folder of the item is not correct, since it does not uniquely identify an actual ancestor of the item.
It's easier to explain that using an example. Imagine the following structure of elements:
Code: Select all
container A (RxPath "container[@title='A'])
\- button 1
container B (RxPath "container[@title='B'])
\- button 2
I.e. you have two containers on one level in the element tree with each a button it it. You want to use button 2 in your recording/code and in your repository you have a folder for container B with button 2 in it. Usually, when you use tracking in Ranorex Spy to add items to your repository, container B will have the correct RxPath "container[@title='B']" to identify the container uniquely.
However, when you change the path for that folder to "container" only (omitting the "[@title='B']" attribute), the folder will actually correspond to the first container in that level, that is container A. Consequently, when you use the repository item for button 2, Ranorex will first search for its parent folder - actually finding container A instead of container B - and will then try to find button 2 using its relative path inside the parent folder. As it can't find button 2 inside container A, Ranorex will try to find button 2 again using its absolute path. The absolute path to button 2 might still be unique (depending on how well defined the relative path for button 2 is) and the button might be found, but you will get the above error to inform you that you need to correct the RxPath for the parent folders of the repository item.
In your case, you will most probably need to correct the path for the "ContainerHBox1" folder and make it unique so no other container is found.
Hope that was clear enough!
Regards,
Alex
Ranorex Team