Hi Swati,

Thank you so much for your comment.

Regarding the issue you faced, I have a question for you.

This table you are trying to extract, are the rows and columns static all the time? or do they change?

Why I ask that is, if the rows and columns are same (content can differ, but the structure should remain the same), then through Form Extractor, we can define a table. This way, you can extract the entire table without specifying custom selection for each field you have in the table. It will be more reliable, accurate and easy too.

However, if the structure is changing, you can think about the Regex Extractor if you can find a pattern that can be applied to extract the text. As you know, similar to the regex we write to extract fields, we can do the same for tables. When using Regex Extractor, in the extractor there is an option to write a regex to identify the table range, and within it, we can write another regex to identify the rows, next the fields.. It's kind of similar to writing regex to separate a string and break it into small chunks.

Refer to this link: https://docs.uipath.com/activities/docs/regex-based-extractor

I will do another article or a video on how to use Regex Extractor in these scenarios soon.