Workday Field XPath Issues

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.4p1

Share all details about your problem, including any error messages you may have received.

I have successfully integrated Workday with IIQ. However, I want to read in one more field from Workday. My Workday admin says that my Workday account has all of the necessary permissions that are needed to read this field. My Workday admin also verified that this is the correct XPath to the field:

<entry key=“NETWORK_ID” value=“ns1:Worker_Data/ns1:Personal_Data/ns1:Identification_Data/ns1:Custom_ID[ns1:ID_Type_Reference/ns1:ID[@ns1:type='Custom_ID_Type_ID']= 'Network_ID']/ns1:Custom_ID_Data/ns1:ID”/>

However, when IIQ aggregates from Workday, this field returns nothing (even though it is populated for many users). I also do not receive any errors during aggregation.

Any help would be appreciated!

2

Hi @vic_rinkenberger

Did you have add this field in schema of you application?

Best regards.

2 Likes
3

Yes, here it is:

<AttributeDefinition name=“NETWORK_ID” remediationModificationType=“None” type=“string”/>

4

I just realized that my XML didn’t show correctly on the original post as it was being interpreted as HTML. It is showing now…

5

Hi @vic_rinkenberger,

have you tried to see if the path is correct with soapUI?

6

Yes, we have verified the path is correct.

7

Hi @vic_rinkenberger - Have you tried retrieving the value in Postman? We have seen that sometimes the custom attributes need to be assigned permissions in WD. Are you using basic auth or OAuth?

8

@vic_rinkenberger is this a custom attribute in workday ? I don’t see NETWORK_ID in workday connector.

if it’s custom attribute then you need to follow __c approach : Configuration to Fetch the Custom Attributes in Workday

NOTE : Custom and calculated attributes added to the Workday schema must have “__c” appended to the field names created in Workday. For example, if you added PREVIOUS_EMPLOYER to Workday, you would add PREVIOUS_EMPLOYER__c in the application schema.

9

I have not tried using Postman, but we have used SOAP UI. Also, we are using Basic Auth.

10

The attribute in Workday is not custom (we just just using an XPath to an existing attribute), but the NETWORK_ID attribute I am setting up to retrieve the attribute IS custom for SailPoint.

And yes, I’m familiar with __c attributes and how they need to be set up.

11

@vic_rinkenberger pls check this link : Account Attributes

I don’t see NETWORK_ID as OOB supported by sailpoint.

12

Right, but I can just give an attribute name such as NETWORK_ID (or LOGIN_ID, or something else), map it to an XPath, and then it should aggregate, right? I’m currently doing that for this attribute and it is working:

entry key=“CFHIREDATE” value=“ns1:Worker_Data/ns1:Employment_Data/ns1:Worker_Status_Data/ns1:Hire_Date”

13

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