Need help with reading in custom fields from Workday

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.4p1

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

I have configured the Workday application and I am reading in the standard Workday fields without any issue. However, when I add in an Integration System ID, Integration Field Override Service, and Integration Field(s), I get an error when aggregating.

I have added only one value to the Integration Field: “Preferred_Name”

I have added that field as a schema attribute with a name of “Preferred_Name__c” and have added the XPath like this:

I have not entered an “Organizational Reference ID” as I did not know what that was. Maybe that is the entire issue.

Anyway, when I run aggregation, I get this error:

[ InvalidConfigurationException ] [ Possible suggestions ] You cannot initiate this action because there are other pending or completed actions for the person that conflict with this one. [ Error details ] Validation error occurred. Invalid ID value. ‘Preferred_Name’ is not a valid ID value for type = ‘Integration_Document_Field_Name’

That error directly relates to the value that I have in the “Integration Field” field on the app. Am I even using that field correctly?

Any guidance would be greatly appreciated. Thanks!

2

Hi @vic_rinkenberger,

more or less, what you have done is ok.
Workday connector works for custom attribute with the name ends with __c or with xpath too.

When you use __c you dont need the xpath, if the workday attribute is build properly(is a big if). Also, you need only of the Integration System ID in most cases.

Organizational Reference ID is another id for reading account from differnt OU in workday(if I remember correctly), so if your target system dont have this division of account, you dont need.

About the error, you are not reading this attribute correctly or are using it incorrectly.
Follow this step for exclude any possible causes:

  • Check if you the permission for reading this attribute
  • Check if this attribute is visible in response(usign soapui for example)
  • Create an attribute without __c and assign it the effective xpath in the response (can you see this topic workday for an example)

later I have 2 questions:

  • Are you using this attribute like identity attribute of app?

image

  • Are you using this attribe in a ReferenceIDMap?

image

2 Likes
3

@vic_rinkenberger You don’t need to add in Xpath.

Check these threads for such error.

workday connector say Account is not a valid ID value for type = ‘Integration_System_ID’ - Compass (sailpoint.com)

Also check if you followed same as mentioned as per connector doc.

undefined
undefined1310×1791 329 KB

2 Likes
4

I actually don’t see a ReferenceIDMap key at all in the config. Is that something that is supposed to be built dynamically?

And yes, I have the Native Object Type and Identity Attribute set as you noted above.

5

yes the ReferenceIDMap is generate automatically when connector read the werday system, but if you want you can change it.

In this case, check the permission, the response and try to use the xpath.
If you want, put here the response and i will help you to build the xpath

6

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