Issues with XPath for Workday Custom Attribute

Hello everyone,

We are currently working on integrating SailPoint IdentityNow with the Workday, We have requirement to add a custom attribute Academic_Rank for all the employees, specifically focusing on retrieving the Academic_Rank_ID from the Get_Academic_Appointee endpoint.However, I’m having trouble with the XPath expression used to extract the Academic_Rank_ID:

We validated the XPath and tested the following expressions in SOAPUI and using various XPath tools, which was showing mapping to the correct data but when we tried the same xpath in IDN it doesn’t work or the data doesn’t come to the attribute.

  1. ns1:Academic_Appointee/ns1:Academic_Appointee_Data/ns1:Appointment_Data/ns1:Rank_Reference/ns1:ID[@ns1:type='Academic_Rank_ID'] - failed
  2. ns1:Academic_Appointee_Data/ns1:Appointment_Data/ns1:Rank_Reference/ns1:ID[@ns1:type='Academic_Rank_ID'] - failed

I also tried including the full response structure in the XPath, but that did not work either:

  1. ns1:Get_Academic_Appointee_Response/ns1:Response_Data/ns1:Academic_Appointee/ns1:Academic_Appointee_Data/ns1:Appointment_Data/ns1:Rank_Reference/ns1:ID[@ns1:type='Academic_Rank_ID'] - failed

Questions:

  1. Are there additional response groups or configurations I should enable to ensure that the Academic_Rank_ID is included in the response?
  2. Do we need to configure anything special if we are trying to access XPaths from outside of the Workers data?

Hi @sanekkanti - have you tried (with __c suffix) on XPath Schema Mapping page.

Hey Aditya, I think that might not work because this is a non worker data and not a Integration Field Override attribute, which are the custom ones where we use the __c

@sanekkanti Did you have the Integration System ID from workday. If you have please map in the config page and add the attribute which you want in account schema with __c suffix. If you don’t have the Integration System ID pls refer the below doc.

Hi @Santhakumar as @aishwaryagoswami mentioned this method did not work because the attribute we are trying to get the data is from non worker data.

@sanekkanti I think the custom attributes will work for non-worker data right? Or am I wrong…

We got to know through SailPoint, It doesn’t support the objects outside of Workers Data to pull as the custom attribute, It’s only restricted to get the the data from Workers Data Object anything other than that there is only one way to get these attributes by creating an other Web-service Connector and pull those attributes and add them to the Identity Profile.

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