Notes
First, a note of general interest: we learned that the IDs that you see in the Finance API right now are expected to remain the same through go-live and beyond. This isn’t a 100% guarantee, but if you’re currently accessing particular records by ID or using those IDs in filters, you can expect those to work the same way and retrieve the same records after the big cutover. This should give you a head start in getting your integrations configured.
This sprint we created a new endpoint for purchase orders. We also continued converting our ETL processes to get their data from Athena instead of directly from Workday. We’ll be chipping away at these steadily for the next few sprints, but we won’t plan on giving detailed updates during reviews, as it’s mostly repetition.
We added some more new fields to sales items: unit of measure, a standard code for the unit of measure, and IDs for related programs, cost centers, funds, and functions. That wraps up the new sales item data we’ve been adding for the last few sprints.
We continued work on a new lastModified field that users can use to generate incremental updates if they like. We’re also working on standardizing the way we store and transmit currency values. We’re now storing them as decimals in our database for more precision – the default type, floating point, has interesting problems when you try to, eg., add a very small and a very large number.
We also continued to experiment more with logging and analytics. This will enable us to spot future performance problems early, possibly before users of the API even notice.
API changes
- New purchase orders endpoint
- New fields on sales items:
- Unit of measure
- UOM EDI code ID
- Program ID
- Cost center ID
- Fund ID
- Function ID