Reporting Behavior for Calculated Fields, Pay Rate, and Per Period Change

We have two changes we are making that we need to make you aware of.

There is a small change in how calculated fields will behave in reporting.

What are calculated fields?

Calculated fields are created using existing fields to derive a new value. For example, you can create a calculated field for when an employee is getting close to retiring. This would be created using the date of birth field and then adding 65 years. The new field can be used in reporting and other areas of Bamboo. It looks like any other field.

In reporting, if you had a calculated field present, it would show up empty unless you saved a new value over the default calculated value. On May 5th we will change reporting to always show a date, whether it is the calculated value or one that has been saved over the calculated value. Currently it only shows a value if a new value has been saved over it.

The employee compensation table will require both the paidPer AND the rate fields, if one or the other is provided. This change will take place on May 19th.

For example, when POSTing to the API endpoint

https://{companyDomain}.bamboohr.com/api/v1/employees/10001/tables/compensation

if your payload looks like this:

<row>
    <field id="startDate">2017-05-01</field>
    <field id="paidPer">Year</field>
    <field id="rate">10</field>
</row>

...then you'll insert a new row, visible on the employee's Compensation table on the Job tab, of $10/Year.

If your payload includes neither paidPer nor rate, you'll be fine. The pay rate will just be blank on the Compensation table like this:

<row>
    <field id="startDate">2017-05-01</field>
</row>

...is just fine.

IF, however, your payload looks like this:

<row>
    <field id="startDate">2017-05-01</field>
    <field id="paidPer">Year</field>
</row>

...or like this...

<row>
    <field id="startDate">2017-05-01</field>
    <field id="rate">10</field>
</row>

...then your API call will be rejected with a 406 NOT ACCEPTABLE status, with the following header returned to you:

X-BambooHR-ErrorMessage: Field errors: Pay (Both paidPer and rate are required when one or the other is given.)