[Feature]: Allow users to select the overflow type in table widget

[dilippitchika]

Is there an existing issue for this?

• [X] I have searched the existing issues

Summary

Today our devs cannot configure table to only have scrolling and no pagination. While this may not be useful to begin with for large data, we plan to expand this and add support for cursor based pagination and infinite scrolling on top of it.

Why should this be worked on?

Allows users to represent data as they wish rather than being constrained with pagination. The workaround today is to enable server side scrolling to see all records in a single page.

Front conversations

[charles-bloomfield]

fyi this would be super valuable for us. Our users much prefer a singular scroll view vs a paginated view. Current work arounds are

• use the pagination feature, which our users don't like
• make the table height really big to fit more rows, but this is still suboptimal because in order to actually scroll the table users have to use the page-level scroll, which means the table header (search/filter/column headers) goes out of view

[justcarroll]

I agree with Charles.. Scrolling ability is super valuable.

[dilippitchika]

Thanks folks, currently we don't have scroll natively yet. This issue talks about making it happen.

But a workaround is-

1. Turn on server side filtering
2. Hide the pagination by turning off the switch in "show pagination" option

Note: This will impact speed of the app for large records as all of them are loaded in the same page. Please be careful.

[charles-bloomfield]

Yea @dilippitchika we are currently using that workaround, which I discovered after my comment last month, and it is working well.