We have a Workday authoritative source and attached is the Manager Correlation logic.
Manager is not populated in SailPoint ISC for some users. When we preview the user in Identity Profile, it shows the preview value but not Identity value.
For most of the users that is working!
We have already performed aggregation from Workday after removing the account but still the manager does not populate. Can anyone help me on this?
Here is the API Docs for how to run an un-optimized aggregation.
Very simple question, does the Manager already have an account in SailPoint?
Yes they already have account in SailPoint
In our environment, we use the following xPath:
"MANAGER_ID": "ns1:Worker_Data/ns1:Management_Chain_Data/ns1:Worker_Supervisory_Management_Chain_Data/ns1:Management_Chain_Data[last()]/ns1:Manager/ns1:Worker_Reference/ns1:ID[@ns1:type='Employee_ID'] | ns1:Worker_Data/ns1:Management_Chain_Data/ns1:Worker_Supervisory_Management_Chain_Data/ns1:Management_Chain_Data[last()]/ns1:Manager/ns1:Worker_Reference/ns1:ID[@ns1:type='Contingent_Worker_ID']",
Have you done a soap call to Workday for the user in question to make sure that the data is returned? I like using SoapUI.
Hello @piyushdiwani ,
If manager is loading for some identities, then try running unoptimized aggregation from Vscode or use Load Accounts API for unoptimized aggregation. I hope this resolve your issue.
-Mehul
The identity attribute ‘Manager Name’ is not populated via the identity mapping window, but instead by the correlation attribute on the source.
Doesn’t matter what transform or value you put in there (on the mapping page), it will only ever show on the preview, and not populate through to the identity cube.
Check what you have on the source
Hi @Dharani, tried un-optimized aggregation but it did not work. Still some users did not populate manager.
Hi @mehuljogi, tried unoptimized aggregation but it did not work. Still some users did not populate manager.
Hi Piyush,
Check the setup in your source
Thank you!
Thank you for responding,
employee number and manager ID are mapped in the IdentityNow Connector correctly and it’s working fine for most of the users, but for some 200 odd users it’s not working.
Check the difference(Attribute values) b/w the working user and not working user.
Also, let me know are those 200 users are from IDN or external?
Hello Piyush,
You can check this issue with SailPoint team, by raising SailPoint support ticket.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
