Notes
We’re happy to report that most of the upstream data issues we’ve seen lately have been fixed. We’re now getting a complete copy of all worktag data every day. This means that:
- FDM combos that used to be improperly marked invalid in our FDM validator will now validate correctly
- Recently added worktags will be visible in the Finance API on the morning of the next business day
- Previously stale award related data (billing schedules & contract lines) is now fresh daily
One problem still remains: sales item and tax code data is still running on cached data. That data is several weeks old at this point. The endpoints still work as expected, but they won’t include any changes made in the last three weeks. EAP is hoping to roll out a fix for this on Tuesday, Oct. 7, at which point it’ll be automatically included in the API results.
We added a number of columns to the response from the journal entry lines endpoint. Previously, there were some columns that were only available in the journal entries endpoint. This data is now included in the lines response as well. Integrators who previously had to use both endpoints should now be able to use only the lines endpoint.
We did some investigation to help us decide on a datastore and HTTP framework for the Locations API that we’re starting work on. We’ve decided to use Amazon’s DocumentDB (MongoDB-compatible) to store the data and Flask to serve it from a lambda function. DocumentDB is new to us, but Flask is familiar.
We fixed a couple of bugs. Previously, using invalid operators on query parameters could result in unexpected behavior. We now return an error message if the operator you specify doesn’t exist. We also fixed an issue with our specification that was causing the example responses to disappear from the developer portal. They’re now back where you expect them.
We also worked on some internal improvements: better error notifications from Apigee, and a refactor in the way we lay out the OpenAPI specification files that will make it easier to update examples.
API changes
- New columns journal entry lines response
- accounting_date
- balancing_worktag_id
- created_on
- journal_number
- journal_sequence_number
- source
- status
- ledger_type
- ledger_period
- entry_memo
- operational_transaction
- originated_by_name
- total_entry_credits
- total_entry_debits
- Using operators other than the defined ones (STARTS_WITH:, ENDS_WITH:, CONTAINS:, LESS_THAN:, & GREATER_THAN:) will now result in an error message