WebElement and WebTable problem

[dutchyes]

Hi,
I am using QTP to click on a row in an IE-browser on a website that has a webtable with rows and columns.
But QTP sees only the WebElement and not the WebTable.
So i can not search the rows or the columns.
And if i try to find a particular WebElement/cell, QTP says the object is not found.
I would expect something like ..WebTable().WebElement(), but instead QTP sees only the WebElement.
Can someone help me so QTP sees the Table object and i can search in the table.

Code:

Browser("Connect").Page("Connect 2").WebElement("WebTable").Click

[sasmitakumari]

See if this thread can help you.
https://www.learnqtp.com/forums/Thread-R...WebElement

[dutchyes]

Thanks sasmitakumari,

The thread helped me out indeed. It talked about getting the webtable object into the repository.
I also found a workaround: make a normal checkpoint (while recording, press insert, checkpoint)
click on a cell/column in the webtable for the checkpoint.
Use the Parameter checkmark in the OR to search for whatever cell-information you want to search and click on that cell.

Code:

Browser("Connect").Page("Connect 2").WebElement("WebTable_4").Check CheckPoint("WebTable")
Browser("Connect").Page("Connect 2").WebElement("WebTable_5").Click

But i like the option to add the webtable object in the OR best.

[sasmitakumari]

while you spy, is it not highlight the area which is a webtable?

[dutchyes]

Yes, i can see with object spy what is the webtable, but the webpage is programmed in such a way that the webtable consists of all seperate element/cells, so in qtp I only can look at the cell-level and do not see the webtable object.

[Arun Prakash]

Hi dutchyes ,

Try to add required web table in OR,then use the below code to get the row with particular text.

Code:

intRowNum=Browser("").Page("").Frame("").WebTable("").GetRowWithCellText(text)

[basanth27]

A Spy shot should help all. Please attach.

[dutchyes]

Hi all,
i did find 2 solutions: with adding the webtable in OR and with a checkpoint.
Thanks all for the input.
So for me this threat can be closed.