and more in a single search tool across platforms. Read the announcement here. |
12/27/2023 02:35 PM
We have created a new connection as type "Workday-SOAP". We are able to create, enable, disable accounts. We are also able to recon accounts. However the attributes & values that we are seeing on the user's workday form are not in alignment with what we have configured in ACCOUNTS_IMPORT_JSON. Is ACCOUNTS_IMPORT_JSON the correct section that maps values coming from workday to the user's workday account form?
example below is what we have set in ACCOUNTS_IMPORT_JSON. However, in the user's linked account, we are seeing other values like department number, email, first name, last name, managers employee number, phone number, city, state, etc.
{
"CONNECTION1": "login",
"REQUESTXML1": "<soapenv:Envelope xmlns:bsvc=\"urn:com.workday/bsvc\" xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\"><soapenv:Header><wsse:Security soapenv:mustUnderstand=\"1\" xmlns:wsse=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd\" xmlns:wsu=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd\"><wsse:UsernameToken wsu:Id=\"UsernameToken-AF7DBE0D8832CC288F150119366041544\"><wsse:Username>${USERNAME}</wsse:Username><wsse:Password Type=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText\">${PASSWORD}</wsse:Password><wsse:Nonce EncodingType=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary\">hVovDsRjkofd3OphNZ83kg==</wsse:Nonce><wsu:Created>2017-07-27T22:14:20.415Z</wsu:Created></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body><bsvc:Get_Workers_Request bsvc:version=\"v31.0\"><bsvc:Request_Criteria><bsvc:Exclude_Inactive_Workers>false</bsvc:Exclude_Inactive_Workers><bsvc:Exclude_Employees>false</bsvc:Exclude_Employees><bsvc:Exclude_Contingent_Workers>false</bsvc:Exclude_Contingent_Workers></bsvc:Request_Criteria><bsvc:Response_Filter><bsvc:Page>${PAGE_NUMBER}</bsvc:Page><bsvc:Count>${PAGE_SIZE}</bsvc:Count></bsvc:Response_Filter><bsvc:Response_Group><bsvc:Include_Reference>false</bsvc:Include_Reference><bsvc:Include_Personal_Information>true</bsvc:Include_Personal_Information><bsvc:Include_Additional_Jobs>false</bsvc:Include_Additional_Jobs><bsvc:Include_Employment_Information>true</bsvc:Include_Employment_Information><bsvc:Include_Compensation>false</bsvc:Include_Compensation><bsvc:Include_Organizations>true</bsvc:Include_Organizations><bsvc:Exclude_Organization_Support_Role_Data>true</bsvc:Exclude_Organization_Support_Role_Data><bsvc:Exclude_Location_Hierarchies>true</bsvc:Exclude_Location_Hierarchies><bsvc:Exclude_Cost_Centers>false</bsvc:Exclude_Cost_Centers><bsvc:Exclude_Cost_Center_Hierarchies>true</bsvc:Exclude_Cost_Center_Hierarchies><bsvc:Exclude_Companies>true</bsvc:Exclude_Companies><bsvc:Exclude_Company_Hierarchies>true</bsvc:Exclude_Company_Hierarchies><bsvc:Exclude_Matrix_Organizations>true</bsvc:Exclude_Matrix_Organizations><bsvc:Exclude_Pay_Groups>true</bsvc:Exclude_Pay_Groups><bsvc:Exclude_Regions>true</bsvc:Exclude_Regions><bsvc:Exclude_Region_Hierarchies>true</bsvc:Exclude_Region_Hierarchies><bsvc:Exclude_Supervisory_Organizations>true</bsvc:Exclude_Supervisory_Organizations><bsvc:Exclude_Teams>true</bsvc:Exclude_Teams><bsvc:Exclude_Custom_Organizations>true</bsvc:Exclude_Custom_Organizations><bsvc:Include_Roles>true</bsvc:Include_Roles><bsvc:Include_Management_Chain_Data>true</bsvc:Include_Management_Chain_Data><bsvc:Include_Multiple_Managers_in_Management_Chain_Data>false</bsvc:Include_Multiple_Managers_in_Management_Chain_Data><bsvc:Include_Benefit_Enrollments>false</bsvc:Include_Benefit_Enrollments><bsvc:Include_Benefit_Eligibility>false</bsvc:Include_Benefit_Eligibility><bsvc:Include_Related_Persons>false</bsvc:Include_Related_Persons><bsvc:Include_Qualifications>false</bsvc:Include_Qualifications><bsvc:Include_Employee_Review>false</bsvc:Include_Employee_Review><bsvc:Include_Goals>false</bsvc:Include_Goals><bsvc:Include_Development_Items>false</bsvc:Include_Development_Items><bsvc:Include_Skills>false</bsvc:Include_Skills><bsvc:Include_Photo>false</bsvc:Include_Photo><bsvc:Include_Worker_Documents>false</bsvc:Include_Worker_Documents><bsvc:Include_Transaction_Log_Data>false</bsvc:Include_Transaction_Log_Data><bsvc:Include_Subevents_for_Corrected_Transaction>false</bsvc:Include_Subevents_for_Corrected_Transaction><bsvc:Include_Subevents_for_Rescinded_Transaction>false</bsvc:Include_Subevents_for_Rescinded_Transaction><bsvc:Include_Succession_Profile>false</bsvc:Include_Succession_Profile><bsvc:Include_Talent_Assessment>false</bsvc:Include_Talent_Assessment><bsvc:Include_Employee_Contract_Data>true</bsvc:Include_Employee_Contract_Data><bsvc:Include_Collective_Agreement_Data>false</bsvc:Include_Collective_Agreement_Data><bsvc:Include_Probation_Period_Data>false</bsvc:Include_Probation_Period_Data><bsvc:Include_Feedback_Received>false</bsvc:Include_Feedback_Received><bsvc:Include_User_Account>false</bsvc:Include_User_Account><bsvc:Include_Career>false</bsvc:Include_Career><bsvc:Include_Account_Provisioning>false</bsvc:Include_Account_Provisioning><bsvc:Include_Background_Check_Data>false</bsvc:Include_Background_Check_Data><bsvc:Include_Contingent_Worker_Tax_Authority_Form_Information>false</bsvc:Include_Contingent_Worker_Tax_Authority_Form_Information><bsvc:Exclude_Funds>true</bsvc:Exclude_Funds><bsvc:Exclude_Fund_Hierarchies>true</bsvc:Exclude_Fund_Hierarchies><bsvc:Exclude_Grants>true</bsvc:Exclude_Grants><bsvc:Exclude_Grant_Hierarchies>true</bsvc:Exclude_Grant_Hierarchies><bsvc:Exclude_Business_Units>true</bsvc:Exclude_Business_Units><bsvc:Exclude_Business_Unit_Hierarchies>true</bsvc:Exclude_Business_Unit_Hierarchies><bsvc:Exclude_Programs>true</bsvc:Exclude_Programs><bsvc:Exclude_Program_Hierarchies>true</bsvc:Exclude_Program_Hierarchies><bsvc:Exclude_Gifts>true</bsvc:Exclude_Gifts><bsvc:Exclude_Gift_Hierarchies>true</bsvc:Exclude_Gift_Hierarchies></bsvc:Response_Group></bsvc:Get_Workers_Request></soapenv:Body></soapenv:Envelope>",
"ACCOUNTMAPPING1": "NAME:Worker_Data.Worker_ID,ACCOUNTID:Worker_Data.User_ID,CUSTOMPROPERTY1:Worker_Data.Personal_Data.Identification_Data.Custom_ID.Custom_ID_Data(ID_Type_Reference->ID=='CustomID_NTID').ID,CUSTOMPROPERTY3:Worker_Data.Personal_Data.Identification_Data.Custom_ID.Custom_ID_Data(ID_Type_Reference->ID=='CustomID_UPN').ID,CUSTOMPROPERTY4:Worker_Data.Personal_Data.Contact_Data.Email_Address_Data(Usage_Data->Type_Data->Type_Reference->ID=='WORK').Email_Address,CUSTOMPROPERTY5:Worker_Data.Personal_Data.Name_Data.Legal_Name_Data.Name_Detail_Data.First_Name,CUSTOMPROPERTY6:Worker_Data.Personal_Data.Name_Data.Legal_Name_Data.Name_Detail_Data.Last_Name)",
"PREFIX1": "wd",
"RESPONSETOTALRESULTS1": "Body.Get_Workers_Response.Response_Results.Total_Results",
"RESPONSEPAGERESULTS1": "Body.Get_Workers_Response.Response_Results.Page_Results",
"RESPONSEDATAPATH1": "Body.Get_Workers_Response.Response_Data.Worker"
}
Solved! Go to Solution.
12/27/2023 08:11 PM
Hello @KTaggart,
May we know why you are not using dedicated workday connector i.e (Workday).As Workday 2.0 provides more flexibility and features compare to Purely Soap Based Workday Connection.
Also can you please brief more about the issue you are facing on which attributed you found is a mismatch in the mapping?
Is ACCOUNTS_IMPORT_JSON the correct section that maps values coming from workday to the user's workday account form?
Yes , That where you define the mapping for account-import.
HR_IMPORT_JSON
JSON containing SOAP Request XMLs and USER Mappings for Users Import
ACCOUNTS_IMPORT_JSON
JSON containing Request XMLs and ACCOUNT Mappings for Accounts Import
For Ref: -
https://docs.saviyntcloud.com/bundle/WD2-v23x/page/Content/About-this-Guide.htm
12/28/2023 06:10 AM
Hello @sudeshjaiswal
In the above I gave value of JSON that we have in our ACCOUNTS_IMPORT_JSON. I am also attaching a screenshot example of 1 user whose workday accout got linked and values that we have observed on his form. All of the values that are present and the # of fields are not in sync with out JSON. Please help confirm how/where this is mapped so if we want to update we can do so accordingly.
Thanks,
Kyle
01/18/2024 05:39 AM
Hi, Please provide the RECONCILATIONFIELD1 in ACCOUNTS_IMPORT_JSON.
01/18/2024 05:43 AM
Make use of workday 2.0 connector which is the latest one instead of using workday_soap. In workday2.0 will be having the two separate parameters for ACCOUNT_IMPORT_PAYLOAD and ACCOUNT_IMPORT_MAPPING