I agree with what @ppr mentioned previously. I think he’s suggesting you don’t really need the find children activity at all, which is what I’m inclined to believe. You need to use an index counter that is shared between the datatable and the web page elements. So your selector might look something like:
<webctrl ... idx='" + indexCounter.ToString + "' ... />
Note that the
idx value may start on 2 or something, and if your
indexCounter variable is zero-indexed you will need to reflect that in the selector as such:
<webctrl ... idx='" + (indexCounter + #).ToString + "' ... />
You can loop until the element doesn’t exist, and if it doesn’t, go to the next page. This would also have to be reflected in the selector though, so you could have two index counters, one that tracks the place in your datatable, and one that tracks your place on the page. So when you go to the next page, reset that variable to the default value again, but retain the index counter that corresponds to the place in the datatable.