SAP source was showing aggregation warning signs that aggregation activity has been skipped due to threshold has been reached we have increased the threshold value and ran the aggregation now aggregation is getting successful but there are no accounts in the source and automatically source is going down and when we test the connection it is becoming successful.
Increasing the threshold allows for more accounts to be deleted which is what you are seeing.
Has anything changed? Can you confirm that you still have security access to get the account data? Have your criteria changed? Have you added any filters?
yes accounts which are not present in the sailpoint will be deleted we have added a filter earlier to aggregate 3 series accounts but in the SAP side accounts are still present.
I would check the filter.
If you are using source filtering, like in the article below, keep in mind that these are the accounts that you want to exclude from SailPoint (not include)
IdentityNow Account Filtering during Account Aggregation - Compass
We are using the below filter
“path”: “/connectorAttributes/account.filterString”,
“value”: “(!(User Name.startsWith("2") || User Name.startsWith("3")))”
we have used it to aggregate 2 and 3 series accounts and it was working fine but aggregation had warning we have increased the threshold of accounts getting deleted in a single aggregation and then later on we are facing this issue and these sources are going unhealthy automatically with no accounts.
Hi @ArjunYV ,
Not able to think of the solution as test connection working fine but no accounts getting aggregated for aggregation.
Can you try removing the filters and run “unoptimized” aggregation? So, we can confirm that the issue with filters or not? Also, any changes made to the account schema?
i have tried running the unoptimized aggregation no changes and there is no change made to the account schema.
There is something else going on with your source. If your source is going unhealthy, it started deleting accounts, and you didn’t change your filter, then you need to look at the source.
- Are you able to test your source successfully?
- Remove the filter.
- Trying aggregating the source. Look in the CCG logs on the VA to determine if you see an errors from the aggregation. See if you see any accounts being processed.
- If you don’t find the error, use this document to patch your source to DEBUG logging:
Enabling Connector Logging in IdentityNow - Compass
- Wait about 5 minutes. Aggregate and check for errors again. If you don’t see any errors or accounts, have your SAP team check their logs.
- If you do some accounts coming in, but are still getting errors. Use Postman/VSCode to change the healthcheck and aggregation timeouts for the source.
Also, you do not need to change the aggregation delete threshold to use filters. With a filter, the full aggregation runs and then uses the filter to remove entries before they are returned to ISC as accounts. The threshold does not apply to the filter because it hasn’t seen the account yet.
Hi Alicia,
we have removed the account filter for the two SAP sources and ran the aggregation we are able to load the accounts basically all the accounts whose Pid doesnt start from 2 and 3 and then we added the filter back which will allow only 2 and 3 but it doesnt seems to be working we disabled the delete threshold and ran the aggregation we have come acrossed that accounts are not getting scanned under aggregation.
What if you try this filter:
((!(User Name.startsWith(“2”))) && (!(User Name.startsWith(“3”))))
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.