[Docs]: Clarify Table selectedRowIndex vs triggeredRowIndex after filter/search

Open Beginner friendly
  • Is something wrong?
#3,075 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Open the Table widget reference at https://docs.appsmith.com/reference/widgets/table and find the blurbs for selectedRowIndex, selectedRowIndices, and triggeredRowIndex. Clarify which dataset each property indexes, using the proposed wording in the issue. The work is done when all three blurbs explain the relevant dataset and triggeredRowIndex specifies that its index is before search, filter, or sort.

Written by the indexing model from the issue text.

Description

Documentation User Education Pod
Problem Statement

The Table widget reference does not say which dataset each row-index property refers to. After client-side search/filter/sort, triggeredRowIndex (original tableData) and selectedRowIndex / selectedRowIndices (filteredTableData) can disagree. Users reasonably treat them as the same kind of index.

Use Cases / User query reference

Pylon ticket: https://app.usepylon.com/issues?issueNumber=3401

Customer used setSelectedRowIndices([Table1.triggeredRowIndex]) so a row-button path could reuse selectedRows for a review table. That breaks after search because selection indexes are filtered positions while triggeredRowIndex is the original tableData index.

Proposed Changes

On https://docs.appsmith.com/reference/widgets/table, update the reference property blurbs:

  • selectedRowIndex — Index of the selected row in filteredTableData.
  • selectedRowIndices — Indexes of the selected rows in filteredTableData.
  • triggeredRowIndex — Index of the triggered row in tableData (before search, filter, or sort).
Checklist
  • Reviewed existing documentation to ensure this request is not duplicated.
  • Attached relevant media or supporting materials like links to the PRD, feature recordings, Slack or Discord links, and any other relevant resources.
Dominant language
MDX
Stars
98
Forks
308
Avg merge
1d 18h
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from appsmithorg/appsmith-docs

All issues in appsmithorg/appsmith-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.