Account aggregation is getting skipped for SAP sources due to error account deletion was skipped for SAP source because the threshold value has exceeded,
Hi @ArjunYV
Increase the threshold limit so that it deletes those accounts. After increasing it, perform an aggregation and adjust the threshold value according to your requirement. This error may arise because you might have changed the correlation configuration and are now trying to aggregate.
Thankyou!
Have you recently changed anything on the source, as we can see 0 accounts scanned? Because of this it is crossing the delete threshold.
Hi @ArjunYV
you’re facing issue in scanning accounts
try this
“!((uniqueName.startsWith(“2”) || uniqueName.startsWith(“3”)))”
Thankyou!
Hi @Gopi
what is the preferred threshold limit at present we need to add we have not changed the correlation configuration but we updated the source account filter to aggregate 3 series accounts.
Hi @ArjunYV
“!((uniqueName.startsWith(“2”) || uniqueName.startsWith(“3”)))”
try the above filter and let me know
Thankyou!
Hi Ankush,
We have modified the account filter under source to aggregate 3 series accounts to the below
“(!(uniqueName.startsWith("2") || uniqueName.startsWith("3")))”
Hi Gopi,
I have tried the below filter as per your suggestion and ran the aggregation
{
“op”: “replace”,
“path”: “/connectorAttributes/account.filterString”,
“value”: “!((uniqueName.startsWith("2") || uniqueName.startsWith("3")))”
}
] Preformatted text
you are trying to aggregate or filter out 3 series accounts? Since your filter has the negative condition.
Hi Ankush,
we are trying to aggregate 3 series accounts.
HI @ArjunYV ,
Make sure the path you are giving is correct. You can check the path using JSON Path finder tool for the JSON output. Also make sure the “uniqueName” attribute is same as in source.
value should be
“(!(uniqueName.startsWith(“2”) || uniqueName.startsWith(“3”)))”
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.