Delimited Connector correlation issues

When I attempted to link the identity attribute to the source attribute. Although the aggregation process was successful, the accounts remained empty. I attempted to correlate the source with several attributes. All of the accounts are pulled in an uncorrelated condition. Both in the tenant and the application, we have the values match. Still, we are having this problem.

Hi , @Navya-Selvaraj
Kindly share your Correlation logic and Account schema of both the authoritative and non authoritative sources

Hi @Navya-Selvaraj,

Please check the account attribute responsible for correlation is being populated properly.

Is it the case where you ran the aggregation and then added correlation logic?

Also please share the correlation mapping that you are using.

Hi @Navya-Selvaraj,

If you think your correlation configuration is correct please try running un-optimized aggregation via API.

1 Like

Hi @Navya-Selvaraj ,

If this is an authoritative source, then before aggregation โ†’ create an identity profile and map it to a source. Then, inside created IP โ†’ in mappings tab โ†’ map the source attributes with the identity attributes. Verify the identity attribute uid is mapped and also the identities should have firstname, lastname, email also the source attribute mapped as accountName and accountId is also mapped with the identity attribute.

If this is a non-authoritative source, then verify the account attribute responsible for correlation is being populated properly. After modifying it, run the unoptimized aggregation via API.

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