Deletion of all accounts during aggregation

[radoslaw_klimkowski]

Dear All,

I just spotten unusal behavior of SaaS Web Custom connector:

• during aggregation i get this warning (deletion threshold is set for 10%, agg is set as paging parent and child for each account)
• aggregation and paging was working normally until 18.08
• postman calls are exactly the same as before, no changes on customer side

Does it really mean, that connector wants to delete 3035 accounts (from 3085)?
Why this error pop out when those accounts are existing on the source (3100)

Paging that i’m using
initial page offset: 0
page size: 50
paging steps:
$limit$ = 50
TERMINATE_IF $RECORDS_COUNT$ < $limit$
$offset$ = $offset$ + 50
$endpoint.fullUrl$ = $application.baseUrl$ + $endpoint.relativeUrl$ + “&limit=50&start_position=” +$offset$

Many thanks for helping on that topic

BR, Radek

[HussainshaSyed001 (Hussainssha Syed)]

just increase it 100% and do aggregation

[radoslaw_klimkowski]

hey @HussainshaSyed001 thanks for advice, i’ve changed threshold and it in fact removed all account, aggreagating olny first 50. Now i know that i have paging issue (aggregated 50 out of 3100)

[HussainshaSyed001 (Hussainssha Syed)]

did you see paging configuration and tried by increasing page size?

[radoslaw_klimkowski]

hey @HussainshaSyed001 - maximum page size is 150 so doesn’t solve my problem.

Does any one know how to incorporate “nextUri” instead of limit/offset ?

[atarodia (Animesh Tarodia)]

TERMINATE_IF $response.nextUri$ == NULL
$endpoint.fullUrl$ = $response.nextUri$

Try this

[radoslaw_klimkowski]

hello @atarodia

this paging script gave me following error

Very possible that bacuse nextUri wasn’t mapped.

As my json response looks like that …

{
    "users": [
        {
            "userName": "user name 1",
            "userId": "416778d7-a0d0-48bd-9db1-d7b93c837091",

        },
        {
            "userName": "user name 2",
            "userId": "9ea09909-92f1-4847-87ad-006559018e69",

        },
        {
            "userName": "user name 4",
            "userId": "278dbff4-5a68-4290-ba25-60cc402c2e56",
            
        }
    ],
   "resultSetSize": "3",
    "totalSetSize": "1463",
    "startPosition": "0",
    "endPosition": "2",
    "nextUri": "/users?start_position=3&count=3"
}

… i tried to map response in following way
Root path remain empty

when removed paging setup - no accounts found
with pagind - again invalid URL

NOTE: when i use this format:

• Root path: $.
• Attribute path: users[*].userName
  i got very same Invalid URL error

[atarodia (Animesh Tarodia)]

Hi,

Looks like the next uri is just returning the relative path. If the relative path is in addition to your base url, then you can try :

TERMINATE_IF $response.nextUri$ == NULL
$endpoint.fullUrl$ = $application.baseUrl$ + $response.nextUri$

[KevinHarrington]

Pretty sure @atarodia gave the correct answer, but just for reference, the script is very touchy about spacing. You may just need to add a space between + and $offset$:

$endpoint.fullUrl$ = $application.baseUrl$ + $endpoint.relativeUrl$ + “&limit=50&start_position=” + $offset$

[radoslaw_klimkowski]

Hello All,

I think i solved the issue. The problem was in Response Information → Root Path.

I makred in yellow change i’ve made. Apparently Sailpoint changed overnight the way that SaaS Web Connector handled JSON filtering.
Paging and Response Mapping remains unchanged .

$limit$ = 50
TERMINATE_IF $RECORDS_COUNT$ < $limit$
$offset$ = $offset$ + 50
$endpoint.fullUrl$ = $application.baseUrl$ + $endpoint.relativeUrl$ + “&limit=50&start_position=” + $offset$

Many thanks for all for involment in this topic.
Best Regards