Data Table Without Pagination Does Not Update Properly Data Source Changes

[hamreen]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Description: When using a Data Table in FlutterFlow without pagination, the displayed rows do not update correctly when new data is added to the data source. The table appears to only accept the number of rows as it was during initialization, preventing it from dynamically adjusting to new data.

When there is no pagination, the number of rows displayed remains fixed as the initial number of rows from the data source.

For example, the data source of a paginated DataTable is a list of string with two records, after running the application when you added more rows to the list the datatable dose not get updated accordingly.

The issue does not occur in a paginated table, which updates correctly.

Expected Behavior

The table without pagination should dynamically update when new data added, just like the paginated table.

Steps to Reproduce

Create a Data Table widget in FlutterFlow.

Set the table’s data source to a list of string with two records.

Create a button to add new records to the list

The non-paginated table does not display the new records correctly.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4glPLq25dgrt9Y7ZDAde9Vv2UsJW02RJc0gNpuZxYYGO/2OpkQZP/RQBJVXNe6d1Z2JVv9nmYx+dXGv+zpDOQHAE+bGL5dypFycArdQnu6b8W7PM6edXN9HZlnDkuVyrSw3B1TLstsWkIW3WD7F+yXEzbbJ7LzNlY7Nc6lNZPMnALmAj+6Xn0Jg1ZSfCvr

Visual documentation

A project demonstrating the issue has been created: Project URL

A recorded video showcasing the issue is available.
https://github.com/user-attachments/assets/6a2ad1c8-098d-47ef-b4c1-1c73f46f4e64

Environment

- FlutterFlow version: 5.2.8
- Platform: All
- Browser name and version: All
- Operating system and version affected: All

Additional Information

No response

[Alezanello]

Hello! 👋

Good news! This is a known issue, and our team is already working on it. You can track the progress here: GitHub Issue #4948.

To keep things organized and focus efforts on the original report, I’ll go ahead and close this one as a duplicate.