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

Community

Connector Improvement: Add Extra Email and Pronoun Fields to Workday HCM

Answered
Anna Scheppele User

1. Please add the "pronoun" field under the Personal Information schema. Having this field is important to properly identify the pronouns people use. I can see the pronoun field in the Workday API: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#person/v3/get-/people/-ID-/personalInformation 

2. The current Person Contact Email Address table is missing key fields to differentiate between work and personal emails and to also indicate which email is the primary email. For example, some workers have multiple work emails (due to name changes), but it is currently impossible to tell which is the most up to date email if multiple are assigned. The Workday API does differentiate between "work" and "home" emails and has a "primary" field that is necessary to determine the correct email. https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#person/v3/get-/people/-ID-/workEmails 

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Erin Fivetranner

    Hi Anna - 

    Thanks for submitting these two requests. These are both great improvements to the connector. I will add these to our backlog and continue to monitor for requests for them. 

    Out of interest, are these in priority requested order? 

    Thanks,
    Erin

  • Anna Scheppele User

    Erin - I would flip the order of priority. Distinguishing between work, home, and primary email addresses is more important than pronouns.

    Also, to add to this, I believe similar work and home flags exist for employee physical addresses as well. Would be great to get those in.

  • Erin Fivetranner

    Hi Anna - Just wanted to follow up on this. The links you shared are for the REST API and our connector uses the SOAP API. 

    We get PERSONAL_INFORMATION data today from GET_WORKER. However the `pronoun` field is not available on GET_WORKER. I do see it in a different endpoint. We will need to see if we can swap out those endpoints. 

    Additionally with regard to your second request. That actually is something that we are working on as part of our larger workday Schema enhancement project that is actively underway. You should see an email about this change in the next few weeks. 

    Best,

    Erin