Notes
Welcome to Workday! This sprint we cut over to the live production Workday tenant. All data in the Finance API is now sourced from our production finance software and is suitable for use in production environments. We encountered a few hiccups during the initial data loads, but most datasets are now available.
The following datasets are not yet available due to the planned cadence of data rollout:
- Billing schedules
- Expense reports
- ISDs
- Sponsor invoices
- Tax codes
In addition to shepherding through the new data, we worked on documentation and fixed a couple of bugs. We made corrections to our OpenAPI specification based on what we learned from our new consistency tools, so be sure to re-download the specification if you want an updated view of what’s available. We fixed an edge case that was causing a rare error in FDM validation, and we replaced the cost center ID that was missing from awards. We also finalized our ETL conversion work. All Finance API data is now sourced from the EAP data lake.
We noted that our endpoints for journal entries and journal entry lines don’t refer to worktags in the same way. For example, the data from journal entries will refer to “FD0001 Balancing Fund”, but journal entry lines refer to “FD0001”. We asked attendees which they prefer, and the general consensus was that API consumers would like to have both the ID and the name of worktags, but in separate fields.
API changes
No structural changes, but all data is now suitable for production use.