Yes I am able to aggregate them into ISC.
HI Piyush. Can you confirm the attribute is suffixed with “__CUSTID” and you have the required PUT permission to the change_other_ids API in Workday? ie, can you update it with Postman using Change_Other_IDs Operation Details?
Hi Jeremy, Thanks for the link.
I have already added “__CUSTID” for the attribute and the PUT permission is also provided to this attribute.
When you say PUT permission to the attribute, you will require PUT permissions to the API. Are you able to test with Postman or equivalent? Also, can you post the XPath you are using for the attribute?
This is the XPATH
ns1:Worker_Data/ns1:Personal_Data/ns1:Identification_Data/ns1:Custom_ID/ns1:Custom_ID_Data[ns1:ID_Type_Reference/ns1:ID[@ns1:type=‘Custom_ID_Type_ID’ and text()=‘Network ID’]]/ns1:ID
and Yes the PUT permission is for the API, but I don’t have a setup for Postman currently.
Try:
ns1:Worker_Data/ns1:Personal_Data/ns1:Identification_Data/ns1:Custom_ID/ns1:Custom_ID_Data[ns1:ID_Type_Reference/ns1:ID[@ns1:type=‘Custom_ID_Type_ID’]=‘Network ID’]/ns1:ID
Hi Piyush - I have a similar requirement and wanted to check If this worked for you ?
Hi @j_place
This X-Path doesn’t aggregate the value in ISC
Check you are using single quotes rather than apostophes
@j_place Thanks for the X-Path, however I had tried this Path before but did not notice any changes, but it worked now.
For info, although some XPaths will work for aggregation they may not work for provisioning as ISC needs to be able to parse the XPath to generate the Change_Other_IDs SOAP Message.