> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/studio/ui-elements/table/example.md).

# Example

| First Name | Last Name | Email                   |
| ---------- | --------- | ----------------------- |
| Ashile     | M.Smith   | <smith.ash@yahoo.com>   |
| Robert     | H.Chan    | <robert.h@outlook.com>  |
| Mark       | F.Flores  | <flores.mark@gmail.com> |
| Leonardo   | Carvalho  | <l.carvalho@yahoo.in>   |

Now, let's consider the above table for extraction.

In the UI element the locator configured should give us the number of rows

#### Approach 1 (When we want to decide what needs to be extracted)

Under the properties section. Below Configure the below

***prop.column:Your\_ProductElement = Your\_UIElement / LocatorType:LocatorValue***

***Ex : prop.column:FirstName = la.firstName***

In the above format we can configure all the columns or the column's we require.

#### Approach 2 (When we want all the columns with auto key names)

If you have written a locator which gives all columns . Configure as below.

***prop.columns.locator =*** ***Your\_UIElement / LocatorType:LocatorValue***

The result for the above prop will look like below

Item1 : value

Item2 : value

Item3 : value

With any approach once all the rows has been extracted. It will check for the below prop

prop.nextPage.link : UI Element / Locator Type : Locator Path

If it was configured it will navigate to each active page in the pagination and extracts the data

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qatts.com/studio/ui-elements/table/example.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
