BambooHR - Tips and Best Practices

  • Concerning /time-offs/{id}/status: once a time-off request is canceled, used, or the date is past, its status cannot be changed. You will get an "Error - Insufficient permissions to perform this action on the request" message.
  • When provisioning a Bamboo HR instance, you must already have at least one employee. This could be confusing because not all users are employees. Accordingly, ensure at least one user has employee access levels.
  • If `meta/users/` is not returning anyone, make sure `access level` has been set for users.
  • Bamboo spells “canceled”, not “cancelled” - this is for filtering on status in GET time-offs and PUT /status.
  • Posting to time-off/history, a “502 ServiceException: Request failed” is returned if the time-off to be updated is not "valid" for any reason, such as the time-off is already used or already been overridden.
  • The Time Off History Override is the exact same as making a manual adjustment to the employee's balance through the UI: Manually Adjust Time Off Balances.
  • Posting to time-off/history/override, a 400 error "Bad Request for Discretionary Types" means you should check the vacation accrual policy for that employee exists Flexible Time Off Accrual Option
  • The Time Off History Entry is a completely different function from the history override. In a nutshell, this request takes a time off request and deducts the time from the employee's balance. Let's say that today you are adding time off requests from last year; first you would need to add the time off requests, then you would need to follow it up with the time off history entry.