@writamb2 It looks like you have UseKeys enabled for your table. Is this really necessary? The automation surface does not support nested keys really well, so if you actually have multiple clones of the same table on a page, I would likely suggest a much more complicated approach.

1. Your automation also does not look complete as you have nothing hooked up to your Equals.
2. You are raising events with a key fitting set to None. This will always default to the first match.
3. There is no wait after the WaitForCreate for the table to allow the children to match, so you might have a timing issue when you start testing.

My suggestion would be to start small. Make sure that you do not need to enable UseKeys for the table itself. Ask your self the following question when deciding whether or not to enable UseKeys; do I need Pega Robotics to attach to multiple copies of this control at the same time? Basically; are there two of these on the same page at the same time? I would build a simple automation to iterate the rows of the table and show a message box or log the value of each cell you care about to make sure everything is functioning as you expect. I would then add the clicking of items within the cells once I was certain I could attach to all the cells I cared about. When you are clicking a link within a cell, be aware if the clicking of the link causes the table to become unmatched. If it does, then you will be changing the list of things you are iterating in the middle of an iteration. If that is the case, you will need to have logic to address that as you cannot iterate a list once you have changed that list.