Retrieve Multiple Bug

(0) Share

Report

Posted on by Sheldon Copper

200

Hi,

I was using context.webapi.retreiveMultiple for retreiving records from CRM, but I am able to retrieve only 500 records the

nextlink attribute is coming as undefined for retrieveMultiple

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (5)

Answers (0)

Sort by

ScottDurow 1,039 on at

Like (0)

Report
Copy link

Link copied!
Can you post your code. I've tried doing this and I get the nextLink fine:

this._context.webAPI.retrieveMultipleRecords("account", "?$select=name", 25).then( function success(result) { for (var i = 0; i < result.entities.length; i++) { console.log(result.entities[i]); } console.log("Next page link: " + result.nextLink); }, function (error) { console.log(error.message); } );

Was this reply helpful? Yes No
Sheldon Copper 200 on at

Like (0)

Report
Copy link

Link copied!

Instead of odata query if we use fetchXml at that time nextlink property is coming undefined.Sorry didn't mentioned it before

Was this reply helpful? Yes No
ScottDurow 1,039 on at

Like (2)

Report
Copy link

Link copied!

Ah right - well for fetchXml queries there is no 'nextLink' - it is a paging cookie that comes back as the annotation '@microsoft.Dynamics.CRM.fetchxmlpagingcookie'

So I don't think that this can be classified as a bug - rather we would need to request a feature to return the pagingcookie.

The work around is to simply use the page and count attributes of fetchxml - rather than the paging-cookie attribute (allbeit not as efficient for large recordsets). If you absolutely needed the paging cookie you would need to hand-craft your request/response using an XMLHttpRequest

Hope this helps

Was this reply helpful? Yes No
Hemant Gaur Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Thanks

@ScottDurow wrote:

Ah right - well for fetchXml queries there is no 'nextLink' - it is a paging cookie that comes back as the annotation '@microsoft.Dynamics.CRM.fetchxmlpagingcookie'

So I don't think that this can be classified as a bug - rather we would need to request a feature to return the pagingcookie.

The work around is to simply use the page and count attributes of fetchxml - rather than the paging-cookie attribute (allbeit not as efficient for large recordsets). If you absolutely needed the paging cookie you would need to hand-craft your request/response using an XMLHttpRequest

Hope this helps

Thanks for the analysis @ScottDurow . You are awesome.

hemant

Was this reply helpful? Yes No
Sheldon Copper 200 on at

Like (1)

Report
Copy link

Link copied!

Thanks 🙂

Was this reply helpful? Yes No