-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetchAll returns no more than 5000 items #79
Comments
@Lebowskovitch can I ask you to try to send the same request manually and see if the paging cookie is in the response? You can catch the request details using Fiddler. |
@AleksandrRogov Ok so I tried to do the request manually with postman and I got the paging cookie, and 5000 items in the value, as expected.
It's like the lib would behave differently in a terminal app. Edit: no worries for the names, it's fake data from faker-js :) |
@AleksandrRogov Hi ! Here is an example of what I see on my side. I'm doing a As you can see, it seems the paging cookie is present in the response, but the |
Ok, so I think I found the issue. I was using the web api with the |
@Lebowskovitch great! i will test the request with |
I tried to investigate further but had to stop at some point. I think it has to do with the responseParams variable, which seems to lose the pageNumber property somewhere before the fetch request. |
ok thanks. I will check that. |
Hi everyone,
I'm facing a weird issue. The same fetchXml query returns more than 5000 items (5482 exactly) in one of our app in production (so it's ok) but when I do the same in a local console app, same version of the lib, same xml (copy paste), same configuration (apparently), it returns 5000, as if the paging info was not returned correctly.
I tried to add a log line to see if the response.PagingInfo was there but it's undefined in the console app.
I don't know where to search anymore. Anyone has an idea on this ?
Thanks !
The text was updated successfully, but these errors were encountered: