Known Issues
Request for multiple persons with no custom field error out
Request for multiple persons with no custom field error out
If you request multiple persons and there are no custom fields, or the api doesn’t have permission to read any custom fields, the request will fail with a 500 error. To work around this, grant the API permission to read at least one custom field.
Resolved
customFields are empty
customFields are empty
customFields are now returned for endpoints that return multiple results. Not only if one person is queried.Requests with modifiedSince include empty objects
Requests with modifiedSince include empty objects
If the data for a non-primal payroll employment changed, the person’s endpoint returned an empty object. The data point is now excluded.
Time bookings day unit is null
Time bookings day unit is null
The
unit field of the main time booking object was always null. The day sums are always returned in hours and minutes. This field has been removed.time-bookings endpoint is not available
time-bookings endpoint is not available
We accidentally named the
time-booking endpoint timebookings. The url has been corrected.additionalAddressInfo is null
additionalAddressInfo is null
additionalAddressInfo is now also populated for endpoints that return multiple results, not just those that return one person.