Bug On rowDatas After Search

## Expected Behavior

## Current Behavior

## Steps to Reproduce (for bugs)

Look at these images.

This is how my table looks like in the first seen and the rowDatas near.

Let's search a data in my table and look again the row Data.

Can you see it? There is a bug. But there is something more. If I searched the data and get TWO ROW, it gives me the true rowData on SECOND ROW. Let me explain myself.

I searched again but this time using the "bil" keyword instead "bilgin".

The result(rowData) is true when the clicked data in second or more row.

## Your Environment

| Tech | Version |
|--------------|---------|
| Material-UI | |
| MUI-datatables | |
| React | |
| browser | |
| etc | |

Start by reproducing the reported search and rowData behavior in the table, comparing a single search result with results containing two or more rows. Trace the edit, delete, or show action that reads rowData and verify that it identifies the clicked searched row rather than the first table row; done means each action receives the corresponding rowData after filtering.

Written by the indexing model from the issue text.