Adding Workday custom attributes that contain spaces

Hi all,

I’m currently working on aggregating custom attributes from a Workday connector. I’ve set up the Integration System correctly and am able to pull a few custom attributes by adding them to the schema in the “__c” format (e.g. “WORKER_STATUS__c”)

However, I’m finding that I can’t use this method to aggregate attributes with spaces in their field name. I can see these attributes the response from “GetWorkers” and have tried to add them to the schema with spaces, enclosed in quotation marks, and with Unicode characters for spaces, to no avail.

Has anyone encountered this scenario before, and if so what was the solution? Any help is much appreciated, thanks!

Hi @chris-hogan You can add attribute name with space but you need to add double underscore (__c) at the end of custom attribute name in schema For ex- Active Status__c. For more detail on it, you can refer- “Configuration to Fetch the Custom Attributes in Workday” at Configuration to Fetch the Custom Attributes in Workday

@chris-hogan @paul_gonzalez - Hi

I am trying to aggregate a custom attribute from Workday.I have done the below steps but it seems to not work.Anu pointer or help here is much appreciated.

1.Added the Attribute in Account_Schema External_Payroll_ID as External_Payroll_ID__CUSTID
2.Added the XPATH mapping in the workday config as

/env:Envelope/env:Body/wd:Get_Workers_Response/wd:Response_Data/wd:Worker/wd:Worker_Data/wd:Personal_Data/wd:Identification_Data/wd:Custom_ID[wd:Custom_ID_Data/wd:ID_Type_Reference/wd:ID[@wd:type=‘Custom_ID_Type_ID’]=‘External_Payroll_ID’]/wd:Custom_ID_Data/wd:ID

Am i missing somehting here . I dont see the values is updated it shows as null for all the user

Thanks !

Hi Chris,

Can you please tell how xpath you used, i am trying to create xpath for custom attributes some how its not working , my xpath i am trying like this
ns1:Worker_Data/ns1:Integration_Field_Override_Data[ns1:Field_Reference[ns1:ID[@ns1:type=‘Integration_Document_Field_Name’]=‘Department_type’]]

Hi Sabthami and Nani,

The issue I was facing ultimately ended up being on the Workday integration side and the Workday SME resolved it. After it had been taken care of, I simply added the attribute to the schema with the “__c” format as Paul had described and it worked as intended with no XPath mapping necessary.

For anyone else encountering this thread: It turned out that the spaces were not a part of the issue and just a red herring. I was able to add the custom attribute to the schema with spaces and all (e.g., “my custom attribute__c”). I tried to delete the thread so as not to cause confusion, but I don’t think that’s possible.

1 Like