Workday SOAP - Parsing user Import XML Response

[Jyostna111]

We are trying to import users from workday using SOAP API.

In the USER_IMPORT_MAPPING, we are able to get the data like email address with a generic notation (Provided in Saviynt Workday connector documentation) like "EMAIL":"Worker_Data.Personal_Data.Contact_Data.Email_Address_Data(Usage_Data->Type_Data->Type_Reference->ID=='WORK').Email_Address".

But as per our requirement, we need to get these kinds of attributes in a more filtered way due to the possibility of having multiples of such attribute elements with different values based on other flags like Primary=1 or Primary=0 and Public=1 or Public=0. Below is the example of one such element from Workday SOAP response:

<wd:Email_Address_Data>
<wd:Email_Address>XYZ@abc.com</wd:Email_Address>
<wd:Usage_Data wd:Public="1">
<wd:Type_Data wd:Primary="1">
<wd:Type_Reference>
<wd:ID wd:type="WID">13wwd12121212121dddc2333</wd:ID>
<wd:ID wd:type="Communication_Usage_Type_ID">WORK</wd:ID>
</wd:Type_Reference>
</wd:Type_Data>
</wd:Usage_Data>

So, please suggest a suitable working saviynt notation in USER_IMPORT_MAPPING which includes these additional filters/conditions.

[timchengappa]

Hi @Jyostna111 

Thank you for your query. We are reviewing this and will get back to you soon.
Apologies for the delay...

[prashantChauhan]

Hi

I tried the same scenario to add a filter on a descriptor by using the USER_IMPORT_MAPPING but it did not seem to work for me as well.

Trying to get more information from the Product team to confirm if this can be supported by the Workday connector or not.

Below are some of the combinations that I tried in USER_IMPORT_MAPPING but it did not populate the field after import-

"EMAIL":"Worker_Data.Personal_Data.Contact_Data.Email_Address_Data(Usage_Data(@Public=='1')->Type_Data->Type_Reference->ID=='WORK').Email_Address",

"EMAIL":"Worker_Data.Personal_Data.Contact_Data.Email_Address_Data(Usage_Data(@Public=='1')).Email_Address",

"EMAIL":"Worker_Data.Personal_Data.Contact_Data.Email_Address_Data(Usage_Data->Public==\"1\").Email_Address",

"EMAIL":"Worker_Data.Personal_Data.Contact_Data.Email_Address_Data(Usage_Data=='Public=\"1\"').Email_Address",

[Jyostna111]

Hi Prashant,

Please provide an update on this.

Regards

Jyostna

[timchengappa]

@Jyostna111 We will get back as soon as we have confirmation from our product team. It is currently being evaluated...

Appreciate your patience, thanks.

[prashantChauhan]

The Product team has asked to get an Idea created for this as this is not supported right now.

Please create an Idea in the Ideas Portal to proceed with this further.

Thanks.

[shibinvpkvr]

@prashantChauhan @timchengappa Thanks. Can you please confirm that for this scenario to be implemented at the moment, we need to use RAAS and cannot use SOAP based connector?  

[prashantChauhan]

Yes @shibinvpkvr 

Since the response of the REST API will differ from SOAP API and there will be no descriptors, I believe you should be able to map the different Email information in RAAS according to the API response with mapping like the below-

"EMAIL": "wd:Primary_Work_Email~#~string",