- First of all once you load the webpage make sure all elements are loaded with property set to ‘COMPLETE’ and check the table element exists or not.
- Send a hotkey ‘home’ and ‘end’ just to be sure.
- While data scraping keep rows as ‘0’ for whole table to be scraped.
That’s all there is to it, but it is better to inspect the table element and see whether the DomXPath is increasing steadily without any abrupt gaps because pattern recognition can work only under the condition that there is no break in continuity.
The workaround would be attribute based extraction and string operation using ‘Find children’ activity and looping through the descendants (you might have to put some conditional statements which will work if the table has loaded properly)
Sometime there might be another DIV inside that table node which might be confusing the data scraper.
Hope this helps