Hello Everyone,
I usually ran disable optimization / aggregation without optimization when I updated Account Schema and the number of Accounts does not match.
I use SailPoint API for CSV Application and for others like SQL Loader Application , Webservices and AD I directly run from VS Code.
I would love to have more information on when and on what condition should a source be aggregated without optimization. And when to use API for disable optimization and when directly.
Thank you
Hi @j1241,
A regular aggregation that you run from the UI is an optimized aggregation, which means the aggregation will process only those accounts that had any change compared to the previous aggregation.
An unoptimized aggregation does the processing on all the accounts that are aggregated, without considering if the account was modified or not. An unoptimized aggregation is usually performed when you make some configuration changes in your source, where you want all the accounts to be processed (eg. modifying a correlation rule, schema change etc.) You can also perform the unoptimized aggregation if you see accounts are not getting correlated or you feel all the accounts need to be processed (eg. an unoptimized aggregation can help in attribute sync of all accounts).
Unoptimized aggregation can be done only with the API call. So if you calling the API directly or through the VS code, the effect is the same as the VS code is also calling the underlying API’s.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.