Does this IDNRuleUtil method “attrSearchCountAccounts” searches against the uncorrelated accounts too?
I have WD source that has 23K accounts.
I have a JDBC source that has 300K accounts.
The accounts in these sources contain a unique id information which is used as a correlation key throughout the org.
Currently 23K workday accounts have their corresponding IdentityNow profiles and their corresponding JDBC accounts have been attached to them. There are still around 277K JDBC accounts that are uncorrelated.
I have an attribute-generator rule in the AD create account profile that checks against this JDBC and WD account ids to generate a new value.
My understanding was that method looks only at the correlated profiles > their accounts. Is this understanding correct or it looks at the uncorrelated accounts too (coming JDBC source)?
attrSearchCountAccounts will consider all accounts in a given list of sources, including uncorrelated ones. Given you correctly configure the Search Attribute Configuration & run an unoptimized aggregation after creating it. You’ll see that search attribute on the /beta/accounts API endpoint.
For example, if you create the Search Attribute Configuration for “promotedEmailAddress,” you’ll see this attribute on each account.
@adunker
I see an issue while using this method. I am generating a unique id value for user at the time of AD account creation.
This method works perfectly when I create one user at a time.
But if I send multiple user creation requests in a single go, my requests don’t know that the unique value is conflicting among themselves. So same unique value is assigned to all of my requests.
Is there a way we can fix this issue in this scenario? Any insights would be helpful.
