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

Community

Connector Improvement: Workday Financial Management LEDGER_ACCOUNT.ID is CODE and the true ID should be added

Not planned
Brad Teague User

In the LEDGER_ACCOUNT table, the ID column is not an ID, it is the account code (e.g. 900600). Typically, IDs in this ERD/schema are Workday IDs (e.g. 3fd202d6593e10019bb507a465620000). In fact, the JOURNAL_ENTRY_LINE table has two columns: LEDGER_ACCOUNT_ID and LEDGER_ACCOUNT_CODE. Using the above examples, the values are 3fd202d6593e10019bb507a465620000 and 900600 respectively. So, intuitively the LEDGER_ACCOUNT.ID column should be the ID and an addition column CODE should be added to contain the code that is currently in the ID column.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Frank Fivetranner

    Hi Brad, 

    Thanks for submitting this request and that makes sense to me. I'll add this request to our backlog. 

    Frank

  • Frank Fivetranner

    Hi Brad, 

    We checked the API docs and the Workday source does not return the WID for the ledger account. See the sample response below and API docs reference: 

    Let me know if you have any further questions. 

    Frank

  • Brad Teague User

    If that is the case, the destination column should be CODE or LEDGER_ACCOUNT_CODE. ID in most of the other tables, if not every other table, in your schema is the Workday ID, specifically in the JOURNAL_ENTRY_LINE.LEDGER_ACCOUNT_ID. Otherwise, I believe this is an oversight on the part of Workday's API. The fact that other tables have an ID that is not retrievable using a Ledger Account API is nonsensical.