Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Workday HCM: add the City column to the candidate table

Answered
Aaron Janaszak User

Connector name:Workday HCM

Table name:CANDIDATE

Column to add:CITY

API documentation link:

 

Additional details:

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Tom Jose Fivetranner

    Hi Aaron,



    This is a valuable suggestion. The request to add the CITY column to the CANDIDATE table for the Workday HCM connector has been added to our feature improvements backlog.



    Could you share more about your use case or any specific challenges you are experiencing due to the absence of the CITY field? Understanding your goals will help us better address your requirements.



    We will provide updates on this thread if there is any progress.



    Thanks,
    Tom

  • Aaron Janaszak User

    I've been working with the Support team, ticket #389681, and Chris Mills on this. Some context I have:


    As suggested, I verified the API response for the Get_Candidates_Request and can confirm that, though the Country_City_Reference is not retrieved from the source. The source is sending the "city" field as a flat field inside the candidate>Candidate_Data>Contact_Data>Location_Data object.
    However, it appears that both city_code and the city are different values. While the city_code field is mapped to fetch codes like GB, FR, etc., the City field in the API response contains city names like Surrey, Paris, etc.