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

Community

Connector Improvement: Workday HCM Connector to support Position history

Answered
Michael Kam User

Hi Fivetran team,

I wonder if it's possible to ingest position_history data from Get_Positions endpoint. Also, I'm wondering how did Fivetran identify which endpoints can we ingest the history data from (for example Get_Workers)? This would help us to assess the endpoint before requesting a feature that might not be feasible.

 

Thank you,

 

Michael

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Frank Fivetranner

    Hi Michael, 

    The reason why we have history for workers is because Workday provides us a separate endpoint to collect history from Workers. That being said we will continue to explore ways to get history from other endpoints if possible. 

    Thanks, 

    Frank

  • Michael Kam User

    Hey Frank,


    Thank for your response and I have another question for my own understanding, although slightly out of topic from this feature request.

    If the history tables come from the Get_Worker_Event_History endpoint, would this mean we could have a reference of the worker event id in the history tables (for example in worker_history)?

    Thanks,
    Michael

  • Frank Fivetranner

    Hi Michael, 

    To address your question on worker_history: not sure if that is possible although it would be a separate feature request. 

    To the request on position_history:

    • Is it important that your history table contain all historical changes or just changes going forward?
    • Is it important that you retain a record of every change? Or would you be okay just capturing history after every sync?

    Thanks, 

    Frank

     

  • Michael Kam User

    Hey Frank,

    I will raise a separate feature request to explore adding event_id in the history tables.

    For your question on position_history:

    • Ideally yes, we want to have all historical changes as this can help us to identify some employee movement process that somehow didn't reassign the employee to a new position, instead editing the existing one. Another limitation that I see right now is when a position has some overlaps, the details that are coming from the API endpoint is only the details of that position with effective date as of now. However, having the ability to track history moving forward is still a win.
    • For the second question, sorry but could you elaborate a little bit more? 

    Thanks,
    Michael

  • Frank Fivetranner

    Hi Michael, 

    Sorry for the late response. To my second question: Would you prefer to have every change included in the tracking of history (e.g. if a record changed 5 times in a minute you want the record of every change that occurred between syncs) or just changes between sync times (aka just a snapshot of the data at every sync)? 

    Frank