Your web site or application generates ID attributes for its elements dynamically. This causes your tests to fail because once the ID attribute for a given element changes, it can no longer be identified.
We recommend that you consider changing your application in order to make it use non-dynamically generated IDs. It will pay off in time saved on automation tasks. However, we realize this will not be an option for everyone. In this case you need to bypass the ID attributes. There are two ways to do this:
Open the Project Settings menu:
Go to Identification Logic from the navigation bar on the left:
This is a list of the attributes Test Studio will use to build the Find Logic for elements when you're recording a test. The attributes are listed in order of priority.
Note: Keep in mind that the Find Expression for a given element will only use two attributes.
You can delete the ID tag from the list altogether or you can can move it further down to decrease its priority. After you've saved the changes, any new tests you record will use the new configuration designed to avoid ID tags.
A recorder step is failing due to a changed ID. If you click on the recorder step from the Steps menu, an Element in the Elements Explorer becomes highlighted in the Elements Explorer:
The highlighted element is the one used in the step. Right-click on it and choose "Edit Element". This will bring up the Find Expression Builder. From here you can edit your Find Expression in order to make it better-suited to your specific automation task. See our article on how to Change How an Element is Found.
The specific solution will depend on your application. In some instances, only parts of the ID will change (e.g. only the prefix or suffix will be different). In this case you can change the condition from "Exact" to "Contains" and exclude all the non-constant parts of the ID from the Find Expression. Ensure the Find Expression is still unique.