Correlation mechanism is not overriding based on the updated information.

[Gopinath]

Hi Team,

We are encountering an issue with correlation. Specifically, the correlation is based on users.email=accounts.customproperty5. When a new account is created and synced, it correlates successfully with the user identity. However, when changes occur in custom property 5 for an existing account, it fails to correlate with the new user identity, instead retaining details from the old user identity.

For example: let's consider the account "Pa_kanes5," initially associated with custom property 5 as "sudheer.kaneti@domain.com" and correctly correlated with the user "kanesu." However, subsequent changes have occurred where "Pa_kanes5" now has custom property 5 set as "gopinath.mattapalli@domain.com" in the target account. Although Saviynt reflects this updated email for the account, it still displays the old username linked to the account, rather than "mattgo." This indicates that the correlation mechanism is not overriding based on the updated information.

Is there any job or task in place that can be utilized to override the correlation of the account with the updated details?

Thanks,

Gopinath
[This message has been edited by moderator to mask email domain]

[PremMahadikar]

Hi @Gopinath ,

Accounts once correlated, remains correlated. It's Saviynt current functionality.

Up-vote the idea - User Account correlation rule not working once the account is already corelated

Manual intervention is the only option.

If this reply answers your question, please consider selecting Accept As Solution and hit kudos to help others who may have a similar problem.

[Manu269]

@Gopinath the only option is via file based upload.

[rushikeshvartak]

If accounts are imported  via Job then correlation can't be overwritten. Please map accounts one time using file import with below config