Correlation Criteria for Flat File not working

Hello Fellow Developers,

I’m encountering an issue with the Correlation Criteria in my flat file source.

Accounts are created in this source through an API call from ServiceNow. The flat file source serves as the authoritative source for creating identities. However, if two accounts in this source share the same name, they get correlated to the same identity. To resolve this, I updated the correlation criteria to match the account ID attribute with the username attribute of the identity. Now, when I create an account with the name “ABC,” it correctly creates an identity with that name. But if I attempt to create another account with the same name “ABC,” it correlates to the previously created identity instead of creating a new one since it has the new id altogether.

Any help would be appreciated as i am trying to go live in production by next week.

Thank you,
pannir

What is the order of your correlation criteria? Is the unique ID the first attribute?

@pannir can you share your current account correlation rule ?

Did you still have the correlation that ISC automatically define by default ?


This is the correlation which I have defined. The username and employee number in my identity is the same and id from account is coming from that API which is mapped to the employee number in identities. But it goes to the default mapping.

Are sure that the id attribute value is differents for your two created accounts ?

yes 100%. Because its is generated from the service now RITM number

Is displayname set as the Account Name in your schema? If so you may want to change that since the default correlation rule is using that attribute for correlation.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.