[BUG]: Loading large datasource fails in FluentDetailsList

[noorsyyed]

Describe the bug
FluentDetailsList control doesn't work on large Dataverse tables having thousands of records, even though "Large dataset paging is toggled on and Page size is set.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Edit mode of canvas app in makers portal'
2. Click on 'Insert and add FluentDetailsList control'
3. Scroll down to 'Dataverse table e.g. Released Products and set DetailsList dataset'
4. set Items property to Products table
5. set columns_Items like below, just for a single column for now to try it out

Table(
    {
        ColName: "crc1d_itemnumber",
        ColDisplayName: "Item Number",
        ColSortable: true,
        ColWidth: 200,
        ColRowHeader: true,
        ColResizable: true
    }
)

6. It isn't loading data , when tried on smaller tables it worked

Expected behavior
Records in table "Released Product" should load
Screenshots

Additional context

AB#3877

[noorsyyed]

Hasn't been assigned yet 😞 can somebody get a chance to triage

[ericgregorich]

I think I'm having the same problems.

[denise-msft]

Are you still seeing this issue in the latest studio version?

[lbuijtelaar]

Same problem here. When I create a new app (release 3.24083.14), insert a fluent list (version 1.1.34) and setup new Records,Fields and Columns in the control, it only works with a small dataset. When I take a "large" dataset (I don't think it is large, but according to Microsoft & PowerApps), it renders blank rows. When I use a Filter() or FirstN() on the dataset, it works, as long as the number of rows is smaller than the [Page Size] in the properties of the control. If I hypothetically set [Page Size] to 7.500 with a dataset (no Filter or FindN) with 6.500, it renders but it is very slow. Please note that when it renders, it will not show more than 500 rows (irrespective of the Data Row Limit setting of the Power App).

I guess with this it should be easy to find to root cause.

[lbuijtelaar]

Also note:

According to Microsoft's documentation on SQL Server Delegation (https://learn.microsoft.com/en-us/connectors/sql/#power-apps-functions-and-operations-delegable-to-sql-server), the Power Fx function SortByColumns() is delegable. That is true, but only if the sort column is a string. If it is an expression, than it is no longer delegable. In the past the Power Apps Studio was not complaining on the following:

SortByColumns(colData,ctxSortCol,If(ctxSortAsc,SortOrder.Ascending,SortOrder.Descending))

Now it is. The only way to do column sorting now is to create a named formula with the Power FX statements for the data source (for example: myData), without the SortByColumns. Then for each column that requires sorting, a switch must be build:

If(ctxSortCol="ID",SortByColumns(myData,"ID",If(ctxSortAsc,SortOrder.Ascending,SortOrder.Descending)),
ctxSortCol="Date",SortByColumns(myData,"Date",If(ctxSortAsc,SortOrder.Ascending,SortOrder.Descending)),
...)

[denise-msft]

Thank you for confirming. Our team is currently investigating. We will keep you updated on our progress.

For anyone who is still struggling, does the modern table component meet your needs? If not, please share the reasoning if possible so we understand which features are important to continue supporting as the delta between the new component.

Also note:

According to Microsoft's documentation on SQL Server Delegation (https://learn.microsoft.com/en-us/connectors/sql/#power-apps-functions-and-operations-delegable-to-sql-server), the Power Fx function SortByColumns() is delegable. That is true, but only if the sort column is a string. If it is an expression, than it is no longer delegable. In the past the Power Apps Studio was not complaining on the following:

SortByColumns(colData,ctxSortCol,If(ctxSortAsc,SortOrder.Ascending,SortOrder.Descending))

Now it is. The only way to do column sorting now is to create a named formula with the Power FX statements for the data source (for example: myData), without the SortByColumns. Then for each column that requires sorting, a switch must be build:

If(ctxSortCol="ID",SortByColumns(myData,"ID",If(ctxSortAsc,SortOrder.Ascending,SortOrder.Descending)), ctxSortCol="Date",SortByColumns(myData,"Date",If(ctxSortAsc,SortOrder.Ascending,SortOrder.Descending)), ...)

@lbuijtelaar please note that the Details List specifically does not support automatic sorting per the documentation. Were you expecting automatic storing to work using SQL as the data source? If so, then please try using manual sorting instead.

The modern table component will support delegable data sources like SQL as well as native (automatic) sorting. Please try it out if you haven't yet.

[lbuijtelaar]

Hi Denise, the modern table component is very nice, but it does not support multi selection of rows to do something useful with these rows. The detaillist supports this and therefore is unfortunately still needed in case of my customers. The alternative (building galeries) is not efficient. So if you want people to switch to the modern table, please add single and multiple select and properties such as "selectitems", etc.

[marco-salazar-encora]

I'm facing this same issue. Modern table loads the records without use but it doesn't have the ability to add an icon o url in one of the columns.