Answered

[BUG?] Dataset paging problem

(3) Share

Report

Posted on by Community Power Pla...

Hi,

I have a dataset pcf control to visualize subgrid data and have a problem with paging. For my visualization i have to load all records of the subgrid. Following code doesn't work correctly with small page size.

public updateView(context: ComponentFramework.Context<IInputs>): void {
 // Add code to update control view

 if (context.parameters.targetDataSet.paging.hasNextPage) {
 context.parameters.targetDataSet.paging.loadNextPage();
 }
 else {
 // context.parameters.targetDataSet.loading == false
 // context.parameters.targetDataSet.paging.totalResultCount == 14
 // context.parameters.targetDataSet.records == 10 Objects
 }
}

In my case the formatting options for the subgrid was set to 4 per default. For example if I increase it to 10 it loads all 14 records. But with page size 4 I'm getting only 10 of 14 records.

Does anyone other had this issues or can explain why it not works with smaller page size?

Current installed cli is 0.3.4 but the project was created with previous 0.2.8 (or so).

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (11)

Answers (1)

AnqiChen on at

Like (0)

Report

hi Dieter,

I am not sure about the saying:

1. In my case the formatting options for the subgrid was set to 4 per default

Would you mind to specify more on how do you achieve this?

2. For example if I increase it to 10 it loads all 14 records

Would you mind to specify how do you increase?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi,
I mean the formatting options of the subgrid and the configurable page size.

Currently I've set it to maximum of 250 but i don't know if there will be same issues if there are more records.

Was this reply helpful? Yes No
AnqiChen on at

Like (0)

Report

hi Diexer,

I assume you are talking about the visual height of the control, not the data page size.

1. For visual part, the height of the PCF control generally be unlimitted. We basically give u a container div, and you could decide the height, it's not related with the formatting option.

2. For data part, the initial data pageSize is set through below, (not related with formatting, which is a visual concept)

Options(Top Right Corner) -> Records per page.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (3)

Report
Ok, but why I'm getting different results with row formatting options of 4 or 10 records per page?
Is the snippet I posted the right solution to load all records behind the configured subgrid view?

EDIT:
This is the reason why I'm believe the subgrid uses the formatting options not the personal options.
If I the check the dataset records inside // TODO line (I believe it should run after paging is complete) there are only 8 records loaded
if (context.parameters.targetDataSet.paging.hasNextPage) {
context.parameters.targetDataSet.paging.loadNextPage();
} else {
Object.keys(context.parameters.targetDataSet.records); // -> 8 Records
}

If I'm increase the options for example to 5 it loads all my 10 records.

I believe that this is a bug but I don't know if it is only in our system or in all others.

Was this reply helpful? Yes No
Verified answer

AnqiChen on at

Like (1)

Report

hi Dieter,

First, thanks for pointing out this, I did test and it is as what you are saying. On form, the dataset page Size seems related with the formatting pane. I was incorrect on this. I need to confirm with other team member on the expected behavior.

Second, regarding your observation,

When the pageSize is 5, it calls loadNextPage and get 5 more records, so it totally get all 10 records

When the pageSize is 4, it calls loadNextPage and get 4 more records, now it sits to 8 records. And then, as it still have 2 more records not loaded, it should get hasNextPage to true and load the remaining records.

At my side, I have simulate the whole process and it did get all 10 records. As this does not repro/happen to me, here is the thing that I wish you could help us to figure out.

1) When it sets to load 8 records, would you mind to check the hasNextPage flag again, is it setting to be true?

2) Our loadNextPage is designed that one page is finished loading, then it should request next page data. Would you mind to have 'context.parameters.targetDataSet.loading' to be false before another page loading?

I apologize for any inconvenience, if it still not quite working, would you mind to have a simplified control solution and share to us. My email is 'achen@microsoft.com' in case you need a private drop

Was this reply helpful? Yes No
Community Power Pla... on at

Like (4)

Report
Thanks a lot!
I had no information about the "dataSet.loading" property.
Seems that my initial code snippet was wrong. Just done same Test. Pagesize of 4, subgrid has total 9 records but with my original code it loads only 6. With the customized code it works well and loads all 9 records.

public updateView(context: ComponentFramework.Context<IInputs>): void { // Wait for dataset loading and trigger loadNextPage() if there is more if (context.parameters.sampleDataSet.loading == true) { return; } if (context.parameters.sampleDataSet.paging.hasNextPage) { context.parameters.sampleDataSet.paging.loadNextPage(); } else { var totalCount = context.parameters.sampleDataSet.paging.totalResultCount; var recordIds = Object.keys(context.parameters.sampleDataSet.records); debugger; } }

Was this reply helpful? Yes No
AnqiChen on at

Like (2)

Report

hi Dieter,

While we are still triage whether the number of records should go with the Form Control Formatting. You could actually update your control's pageSize

Here is the way, when the control stop initial loading

You could use

1) context.parameters.targetDataSet.paging.setPageSize(<big number>)

and then call 2) context.parameter.targetDataSet.refresh()

Then the pageSize should be updated. If there still more than expected number of data, you could continue use loadNextPage to load next <big number> size of data

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi,
thanks for the information but since I realized my paging problem I had increased it already to maximum of 250. In most of my cases it should be enough. I will definitely include the loading condition inside updateView.
I just though that this is a bug and should be reported 😉

Regards

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
hey Dieter-aXon,
i have a problem in power apps,
i have created a canvas powerapps and published it but when ever the person with wome i have shared the app is opeing the app it is showing several errors with the names of tables used as data base as they are not supporting, however the app is running perfectly with my login profile and for those who are other users its now working.
please help me out of it.
Thanks in advance.
@Anonymous wrote:
Hi,

I have a dataset pcf control to visualize subgrid data and have a problem with paging. For my visualization i have to load all records of the subgrid. Following code doesn't work correctly with small page size.

public updateView(context: ComponentFramework.Context<IInputs>): void { // Add code to update control view if (context.parameters.targetDataSet.paging.hasNextPage) { context.parameters.targetDataSet.paging.loadNextPage(); } else { // context.parameters.targetDataSet.loading == false // context.parameters.targetDataSet.paging.totalResultCount == 14 // context.parameters.targetDataSet.records == 10 Objects } }
In my case the formatting options for the subgrid was set to 4 per default. For example if I increase it to 10 it loads all 14 records. But with page size 4 I'm getting only 10 of 14 records.

Does anyone other had this issues or can explain why it not works with smaller page size?

Current installed cli is 0.3.4 but the project was created with previous 0.2.8 (or so).

Was this reply helpful? Yes No
Hemant Gaur on at

Like (0)

Report

@Anonymous Canvas apps does not has PCF support yet so this question should be posted on PowerApps maker/general forum .

My guess is that you are not sharing connectors inside the app.

Hemant

Was this reply helpful? Yes No