Steps to reproduce:

1. Record a click step against some element with an unique attribute (e.g. id="myId").
2. Copy and paste the step and convert it into code.
3. Add a local data source column id with "my" value only.
4. Edit the element's find logic to use that column for ID.
5. Change the find rule from exact to contains for the ID.
6. Run the test.

Actual: The recorded step passes, however the coded step fails saying it looks "id exactly my" (i.e. changing the find rule from exact to contains doesn't affect the coded step with the same element). This doesn't happen if the element doesn't use a data driven find logic.

Expected. Both steps should pass.

Note: The above behavior is reproduced if the element is referred from multiple steps in the project. In the case the element is used in a single step changing the find logic from exact to contains for the data driven part works fine.