UKG Pro Core HCM connector Account Schema

[Sushantmr (Sushant Maharjan)]

Hi All,

The “UKG Pro Core HCM” connector has the firstName attribute configured as the Account Name out of the box. Consequently, when multiple users share the same first name, the accounts from UKG correlate with an existing identity instead of establishing new ones. This appears to be a significant limitation in the connector. Has anyone encountered this issue, and if so, how was it resolved?

Furthermore, the article below recommends mapping the Account Name to an attribute that is ensured to be unique. This doesn’t appear to be the case for the out-of-the-box (OOTB) UKG connector, as multiple users can share the same first name.

Source Account Schema Best Practices

Thanks,
Sushant

[ksbagade (Kartik Bagade)]

Hi @Sushantmr,

From my understanding, you want to create identities from a UKG Pro Core HCM source.

In the article shared in your post, it is recommended to keep the Account Name assigned source attribute unique due to the default correlation logic present:

This would mean that before an identity is created, it would check if there is an existing identity matching the attributes displayName (source) to the name (identity).

This can be rectified by changing the assignment of the Account Name to a unique attribute. This will make sure that the account does not get correlated to an existing identity, and if all necessary source attributes are present, the identity should be created.

It is not a limitation of IdentityNow, just preconfigured default behavior.