Help with WebService Paging

Do you mean the id generated on the application side?

This app creates a unique id when an account is created. I checked all the ids returned and they are unique.

I meant that maybe the application have repeated id or the mapping is only capturing 178 because the rest does not have the mapped id.

One more request - can you paste sample payload you are receiving from your api? - like first page

This is what gets printed out from the after operation rule

2024-04-16T05:05:16,815 ERROR QuartzScheduler_Worker-2 connector.webservices.v2.RequestOrchestratorV2:166 - xxx Starting after operation rule
2024-04-16T05:05:16,831 ERROR QuartzScheduler_Worker-2 connector.webservices.v2.RequestOrchestratorV2:166 - xxx rawResponseObject {
“totalCount”: 1415,
“pageSize”: 100,
“pageIndex”: 1,
“startAt”: 1,
“records”: [
{
“attachDocument”: null,
“barcode”: null,
“building”: null,
“cellPhone”: null,
“consolidatedMedicalReportDate”: null,
“dateOfHire”: null,
“dateOfTermination”: null,
“declaredPregnant”: false,
“department”: null,
“division”: {
“code”: “03”,
“description”: null,
“id”: 4520
},

hey @ralfonse ,

What about the APi response?

Best!

This is a sample of what I get when I call it from python.

\getAll.py
{
“totalCount”: 1415,
“pageSize”: 100,
“pageIndex”: 1,
“startAt”: 1,
“records”: [
{
“attachDocument”: null,
“barcode”: null,
“building”: null,
“cellPhone”: null,
“consolidatedMedicalReportDate”: null,
“dateOfHire”: null,
“dateOfTermination”: null,
“declaredPregnant”: false,
“department”: null,
“division”: {

hey , try this one

##################PAGING

$page$ = 1
$pg_limit$ = 100
TERMINATE_IF $RECORDS_COUNT$ < $pg_limit$
$pg_offset$ = $pg_offset$ + $page$
$endpoint.fullUrl$ = $application.baseUrl$ + “api/Employee?pageSize=100&pageIndex=” + $pg_offset$



Context URL

api/Employee?pageSize=200&PageIndex=1

Hi All,

I’m also facing the issue whenever i try to preview nothing displays in preview section but when i do single user preview it is working. i have not set any kind of pagination. Application we trying to integrate is quantum and pleas find below context url
“/quantum/odata/user/”

It’s not pagination issue. If you would see some results but not all of them then it would be because of pagination.

In your case it looks like it is an issue with operation definition or response mapping. It would be good if you could add here this information - operation definition or whole app definition.

If you have link to quantum documentation that would also be great.