We are currently in the process of integrating UKG through the use of the OOTB “UKG Pro Core HCM” connector. While we have successfully aggregated accounts, the connector is only retrieving 200 records, despite our target having more than 200 records.
I have raised a support case with SailPoint, and they informed me that pagination steps need to be configured for the OOTB UKG connector, a task they will handle through ES.
Despite thorough reviews of the connector guide, there is no indication in the documentation that pagination needs to be configured for the OOTB connector. I’m curious if anyone has experience using the OOTB UKG connector and has successfully aggregated more than 200 user accounts.
Hi @Sushantmr, UKG Pro Core HCM connector is capable for aggregating all the accounts irrespective of page size value. But in this case, it looks like an issue with the mismatch in the header as per the response of UKG API (might be tenant specific). I am actively engaged with this one and we are coordinating with UKG. I am aware you already have a support ticket opened, so you will get further updates and resolution via that.
This issue is identified as UKG tenant specific and we also shared this feedback to UKG. However, we already taken care of such scenarios in our connector and changes are now available for everyone in production and sandbox instances. Thanks!