This section covers the ways data can be accessed once it has been supplied to the grid.
Each time you pass data to the grid, the grid wraps each data item
For example if your data has 20 rows, then the grid creates 20
rowNode wrapping one item of your data.
It is sometimes handy to access these
rowNodes. One example where it is handy
is if you want to select a row, you can call
to select it. This section details the different ways a
rowNode can be accessed.
The following methods are provided for accessing the individual
A deeper explanation of these methods, along with examples, are provided
Accessing Row Node API Methods
|Returns the row node with the given ID. The row node ID is the one you provide with the callback |
|Iterates through each node (row) in the grid and calls the callback for each node. This works similar to the |
|Similar to |
|Similar to |
|Similar to |
|Returns the displayed |
|Returns the total number of displayed rows.|
|Get the index of the first displayed row due to scrolling (includes invisible rendered rows in the buffer).|
|Get the index of the last displayed row due to scrolling (includes invisible rendered rows in the buffer).|
Accessing RowNode by ID
The easiest way to get a
rowNode is by its ID.
The ID is either provided by you using the grid callback
or generated by the grid using an internal sequence.
Accessing the rowNode by ID is available in the Client-side Row Model only.
Sometimes you may want to iterate through all the rowNodes in the grid. This can be done using the grid's iteration APIs. The iteration APIs go through every rowNode, regardless of whether the rowNode is displayed or not. For example if grouping and the group is closed, the group's children are not displayed by the grid, however the children are included in the iteration 'for-each' methods.
All of the methods above work with the Client-side
Row Model. For all the other row models (Viewport,
Server-side) the only method that is supported
api.forEachNode() and that will return back row nodes that are loaded into
browser memory only (as each of these row models use a data source to lazy load rows).
Example Using For-Each Methods
The example below shows the different for-Each API methods as follows:
- For-Each Node: Prints out every row in the grid. It ignores filtering and sorting.
- For-Each Node After Filter: Prints out every row in the grid, except those filtered out.
- For-Each Node After Filter and Sort: Prints our every row in the grid, except those filtered, and is the same order they appear in the screen if sorting is applied.
- For-Each Leaf Node: Prints out every row in the grid except group rows.
In the example, try applying some sorts and filters, and see how this impacts the different operations.
Accessing Displayed Rows
Displayed rows are rows that the grid tries to render. For example, if you have a group that is closed, the children of that group will not appear in the displayed rows. The grid renders the displayed rows onto the screen.
The displayed rows have indexes. For example, if the grid is rendering 20 rows, then will have indexes 0 to 19.
You can look up the rows by index. This is dependent on anything that changes the index. For example, if you apply a sort or filter, then the rows and corresponding indexes will change.
Accessing displayed rows works with all row models.
Accessing Displayed Rows Example
The example below demonstrates the following:
- Get Displayed Row 0: Returns back the first row in the grid. This is not impacted by what page you are one, eg if you navigate to the second page, this method will still return the first row on the first page. If you sort, the first row will be changed.
- Get Displayed Row Count: Returns back the total number of rows across all pages. If you filter, this number will change accordingly.
- Print All Displayed Rows: Demonstrates looping through all rows on the screen across all pages.
- Print Page Displayed Rows: Demonstrates looping through all rows on the screen on one page.