Share all details related to your problem, including any error messages you may have received.
Hello all- so myself and the Workday team have run into an issue. We are trying to bring in Secondary Job Title data (JOBTITLE_2__c) into SailPoint to map to an attribute for a project. The issue we are having is it is only bringing in (JOBTITLE_1__c) but I do see from aggregating a few users that it is bringing in JOBCODE_1__c AND JOBCODE_2__c so Im not sure why it wouldn’t bring in the JOBTITLE_2__c field. The JOBCODE2 is the job code for the secondary job title that we are looking for but it’s not being brought in for some reason.
We have an Integration System set up and have domain read rights with the service account we are using.
Hi @colsmith
To re-confirm, did you updated the Integration System with the JOBTITLE_2__c attribute and it is matching exact name as in the SailPoint application Schema?
if I understand you some users with JOBTITLE_2__c valued and other without.
In this the first control is check if i workday are present those values for the users they miss.
Make a soap call for those users an see if the values and the key are present in the integration filed section.
The mapping of integration filed in SP, sometime could be a problem because those attributes are not properly standar attribute in workday.
Also, if those attributes are not build correctly (in WD) the mapping with __c, fails.
You can try to mapping with the xpath. In this topic I explain a little how do:
but first of all, check the data in workday with soap
