Account filter under SAP source modification

[ArjunYV]

How can I update the source account filter string in SailPoint (configured in the backend, not through the UI) from the old value (!(uniqueName.startsWith(“2”))) to the new value (!(uniqueName.startsWith(“2”) || uniqueName.startsWith(“3”))) using Postman or any other API?

[2022Sandeep123 (Sandeep Patel)]

Hello Arjun,
You can achieve this through Postman and ISC API. Also note that filterString works differently in ISC (Accounts which match the filter string will be filtered. Accounts which do not match, will be sent to IdentityNow as normal). Are you trying to filter out uniqueName.startsWith(“2”) || uniqueName.startsWith(“3”) and not bring it in to SailPoint?

Thanks!!
Sandeep

[ArjunYV]

We would like to have both the 2-series and 3-series accounts aggregated. Currently, we are only seeing the 2-series accounts due to the account filter in place. Could you please provide us with the API that can be used to accomplish this aggregation for both account types?

[2022Sandeep123 (Sandeep Patel)]

Hello Arjun,

Api: https://tenantname.api.identitynow.com/beta/sources/sourceid

use ‘Content-Type: application/json-patch+json’ in Postman Header
In Postman Body (Select raw and paste below code)
[
{
“op”: “add”,
“path”: “/connectorAttributes/filterString”,
“value”: “(!(uniqueName.startsWith(\“2\”) || uniqueName.startsWith(\“3\”)))”
}
]

Once you done with API. Run the SAP aggregation to see if you can pull 2 and 3 series users.
Sandeep

[ArjunYV]

Hi Sandeep,

We are receiving this error in postman when we made a call.

[ArjunYV]

Hi Sandeep,

This is what we have currently placed in our source,

“account.filterString”: “(!(User Name.startsWith("2")))”,

[santupatel2025 (Santosh Patel)]

Hello Arjun,

It looks like you are using Content-Type as application/json in the Postman Header. For PATCH operation always use Content-Type as application/json-patch+json".

Let me know

Thanks
Santosh

[ArjunYV]

Hi Santosh,

I have tried the header which you gave and received the below error.

[ArjunYV]

Hi All,

This is what we have currently in the source which is stopping 3 series accounts to get aggregated.

[Abhishek_1995 (Abhishek Kumar)]

Hi @ArjunYV,
The body you are using in postman is it correct. i think the double quote you are giving its wrong please check and type by your own.

please check the screenshot for your reference .The body should look like this.

Thank you!

[ArjunYV]

Hi Abhishek,

I have given the below body and it is updated but after running aggregation still 3 series accounts are not getting aggregated.

[
{
“op”: “replace”,
“path”: “/connectorAttributes/account.filterString”,
“value”: “(!(uniqueName.startsWith("2") || uniqueName.startsWith("3")))”
}
]

[Gopi2000 (Gopi S)]

Hi @ArjunYV

you’re facing issue in scanning accounts
try this
“!((uniqueName.startsWith(“2”) || uniqueName.startsWith(“3”)))”

Thankyou

[Abhishek_1995 (Abhishek Kumar)]

Hi @ArjunYV,
In postman now you are not getting the 405 error code. In postman the json body i provide it work in the postman.

Thank you!