Notes
In this sprint, we did some investigative work around how we’ll present hierarchies in API results. Several Workday worktags (most notably cost centers) are organized into multi-level hierarchies for reporting and related purposes. We demonstrated a proposed structure that would use hierarchical JSON structures to show multiple levels of parent & child relationships. This has the advantage of being easier to parse in some contexts, but doesn’t strictly follow the JSON:API standards, which require a flat structure. We’re still considering options for the design, so let us know if you have thoughts about what would work best for your use cases.
We’ve decided to standardize on camelcase as our formatting for attribute names. The old dttm_loaded attribute on FDM records has been renamed to dttmLoaded to bring it in line with this standard. If you have that attribute name hardcoded, you’ll need to update it in order to point to the new name.
We’ve started the process of giving users some visibility into our ETL process. We’re now storing timestamps and status messages in our internal product data store. The next part will be to give you a way to query those records from the API. This will let you do things like verify that our process is up to date with the records you expect. On our side, we’ll also be able to use it for some internal alerting and quality control measures.
API Changes
-
dttm_loadedattribute is now nameddttmLoadedfor consistency with other attribute names