Workday fetching custom attributes not working

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hi all,

Hope everything’s well.
I’m sorry for open this question but I’ve tried everything following the documentation and couldn’t get the results.
We have a working Workday connector. We can read accounts with all the information added to them.
Now we need to add four custom attributes, for which I’ve provided the Workday admin the IdentityNow documentation that explains the required configuration that must be done in Workday.
He sent me Integration System ID, which I’ve already added to the Aggregation settings in the source, and the XPATH.
The XPATH he sent looks like this:
ws:Worker_Sync/ws:Worker/ws:Additional_Information/ws:Level_5

so, following the documentation, I’ve changed it to:
ns1:Worker_Sync/ns1:Worker/ns1:Additional_Information/ns1:Level_5

I’ve added a new attribute for this with “__c” at the end, in the schema and in the mapping.

image

image
image2451×88 2.56 KB

Ran an aggregation but got no results. These 4 attributes are empty in the account.
Made sure with the workday admin that the service account we’re using has the correct permissions. He also sent me an image where I can clearly see that the user has values in these custom attributes.

What am I missing here?
Thank you all in advance for your kind help.

2

Hi @ninfante_solidigm,

Please try to enable log and see if the details are coming properly and the mapping that you are giving is able to pick the target attribute.

Also, you may use below two discussions for XPATH mapping related issue.

Thanks

3

Hi, thank you for your reply.
I’ve enabled the logs and got the following:

..."level":"TRACE","IdentityIQ":"8.3p4 Build ...","message":"Exiting lambda$getObjectFromXMLResponse$49: Arguments => 123456, LEVEL_6__c, Returns => For Worker Id [123456] unable to fetch Attribute [LEVEL_6__c] Please check provided XPATH or check whether worker [123456] have permission to access [LEVEL_6__c]","pipeline":"1.8.1","@timestamp":"2024-06-03T22:10:15.454Z"....

The same comes in the other 3 attributes. So either we don’t have permissions to read these attributes or the XPATH is wrong. I have my doubts about the last option, since he provided me a screenshot showing the XML object. Something like this:

<ws:Worker_Sync"	xmlns:xsi="http://www.w3.org">
	
	<ws:Header>
		<ws:Version>xx.x</ws:Version>
		<ws:Prior_Entry_Time>xx.x</ws:Prior_Entry_Time>
		<ws:Worker_Count>xx.x</ws:Worker_Count>
	</ws:Header>
	<ws:Worker>
		<ws:Summary>
			<ws:Employee_ID>123456</ws:Employee_ID>
			<ws:Name>Maradona</ws:Name>
		</ws:Summary>
		<ws:Eligibility>true</ws:Eligibility>
		<ws:Additional_Information>
			<ws:Level_6>3</ws:Level_6>
			<ws:Managed_Org>Arg</ws:Managed_Org>
		</ws:Additional_Information>
	</ws:Worker>
</ws:Worker_Sync>

I’ll be reaching out to him to check this, but do you think that something else can be happening here?
Really thank you for your help.

Nico.

4

Hi @ninfante_solidigm,

Can you try to pull the record via SOAP UI or Postman and validate the XPATH.

It will validate if it is about permission or not.

Thanks

5

The xpath must be :

/ws:Worker_Sync/ws:Worker/ws:Additional_Information/ws:Level_6
6

I had similar issue and fixed in by removing references to custom calculated fields (with __c suffix) on XPath Schema Mapping page.
You only need to define it in connector’s Account Schema page.

7

I had to open a ticket with support. It looks like the connector is not working as expected and the engineering team is taking care.
Thanks all for the replies.

1 Like
8

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