Coupa pagination issue only returning first page records i e 50

[amulpuru (Avinash Mulpuru)]

Hey Sailors,

We have configured ws connector coupa APIs

While performing account aggregation we’re only getting 50 records i.e first page records and page size is 50

we don’t have any reference attributes for page number or page count or number of records or next or previous neither in response or nor in response headers of account aggregation

I tried pagination steps no luck as there no reference for count or page

Post last page we are getting [. ] As response

Is there any way to I have counter and append 50 per iteration and Hard stop at post last page i.e response → [. ]

Thanks in advance

Avinash Mulpuru

[trettkowski (Tyler Rettkowski)]

Hi @amulpuru

Try these pagination steps. I have a Coupa WS connector in my environment and it works well with this pagination. This is assuming your baseUrl looks something like this: https://<ENVIRONMENT>.coupahost.com/api

TERMINATE_IF $RECORDS_COUNT$ < $limit$
$offset$ = $offset$ + $limit$
$endpoint.fullUrl$ = $application.baseUrl$ + "/users?offset=" + $offset$

Let me know if this works for you or if you have any questions!

[amulpuru (Avinash Mulpuru)]

Hi @trettkowski,thanks for quick response

I couldn’t see $RECORDS_COUNT$ in response or response headers can you please help me walk through this variable and its value population please

[trettkowski (Tyler Rettkowski)]

RECORDS_COUNT is an OOTB variable that SailPoint provides. You can see some mentions of it in the documentation:

Paging Based on Limit-Offset

[amulpuru (Avinash Mulpuru)]

Hi @trettkowski ,
still no luck

for context url I have tried both
/users

/users?limit=$limit$&offset=$offset$

is there anything im missing here

[ryan_toornburg]

Try with 50 offset and 50 page size.

[amulpuru (Avinash Mulpuru)]

Hi @ryan_toornburg no luck tried

[ryan_toornburg]

In the paging steps add this to the top
$limit$ = 50

[ryan_toornburg]

This has api, but if that is in your base you can remove it.

$limit$ = 50
TERMINATE_IF $RECORDS_COUNT$ < $limit$
$offset$ = $offset$ + $limit$
$endpoint.fullUrl$ = $application.baseUrl$ + “/api/users?limit=” + $limit$ + “&offset=” + $offset$ + “&type[blank]=true”

[amulpuru (Avinash Mulpuru)]

does these steps work for ws SaaS connector too ,still no lcuk

[ryan_toornburg]

Have not tried it on SaaS. I know the Coupa direct connector handles the paging, however I believe that is a separate license to enable on ISC.

[ryan_toornburg]

@amulpuru - If you do a direct GET with Postman setting the Limit to 50 and offset to 0 do you get all the results?

[amulpuru (Avinash Mulpuru)]

Hey @ryan_toornburg and @trettkowski ,

These steps are not working for ws Saas connector moved conection from saas to va based ironically steps provided by @trettkowski , has worked for me but my question is why same paging steps are not working as expected in ws SaaS connector was it a bug on SailPoint Ws SaaS please any from SailPoint help we understand better why same paging steps are not working for ws SaaS

[ryan_toornburg]

@amulpuru - you raise a really great question. We have seen that there are some differences in behavior between some of the SaaS and VA based connectors. It is not entirely clear as to why. Definitely a topic worth pursuing.

[amulpuru (Avinash Mulpuru)]

Hey both,

I would like to keep this thread open to know the root cause,FYI

[ryan_toornburg]

Hi @amulpuru one other thing you can try on the Saas Connector paging. This forces the limit in.
TERMINATE_IF $RECORDS_COUNT$ < $limit$ $offset$ = $offset$ + $limit$ $endpoint.fullUrl$ = $application.baseUrl$ + “/api/users?limit=” + $limit$ + “&offset=” + $offset$