Pagination Issue for Web Service Connector

poojakumari85 · May 21, 2025, 2:07pm

Hi,

I have configured web service connector and it has 138 accounts as per response from postman. But when I run aggregation in SailPoint, I’m getting only 100 accounts. I added the pagination configuration as below, but still the accounts are not getting pulled.

TERMINATE_IF $NO_RECORDS$
$offset$ = $offset$ + 100
$endpoint.fullUrl$ = $application.baseUrl$+“scim/v2/users?startIndex=”+$offset$

Any help is much appreciated.

Thank You
Pooja

sidharth_tarlapally · May 21, 2025, 2:13pm

Hello @poojakumari85

If you are able to get 138 records from postman , It doesn’t seem like pagination issue for me . What is the accountId attribute in the Schema ? Check if all the accounts has this attribute value .

Thanks
Sid

poojakumari85 · May 21, 2025, 2:33pm

there is a param which I add called “startIndex” which pulls all the users.

sidharth_tarlapally · May 21, 2025, 2:37pm

@poojakumari85

Can you show the screenshot of postman please?
I want see the URL and params on postman side . In the response you are getting from postman , check if all the accounts has userName attribute .

poojakumari85 · May 21, 2025, 2:42pm

sidharth_tarlapally · May 21, 2025, 2:54pm

@poojakumari85
can u confirm if all the records have userName values ?

poojakumari85 · May 21, 2025, 3:03pm

No, only 100 users have username but count shows 140

sidharth_tarlapally · May 21, 2025, 3:09pm

@poojakumari85

So this is the reason we see only 100 accounts on the Sailpoint .

The account Id on the Schema must be a uniquely Identified and Not Empty attribute on the application , only then it is counted as account .

Check if the userName is uniquely identified attribute or if there is some other attribute which is so .

suren_info · May 21, 2025, 3:56pm

I have the similar issue after 8.4P2 upgrade and working with sailpoint support case.
As alternative, for applications with lesser accounts try to set the limit on the response.
eg: /users?max=500

Thanks,
Suren