ENG-8320 Support People Attribute Field Creation

Story

As a user, I want to create and update my Custom People Attributes via the API

so that I can bulk-manage and bulk-update my employees' custom people attributes

in an efficient way.

As a user, I want to know when and how my API updates for People Attributes

failed so that I can make adjustments and try again.

1. If a new custom field is recognized in an API call, we will create the field

for the user.

2. If an existing custom field is recognized in an API call, we will update the

field for all relevant users.

3. If a user attempts to import a new custom field and data with inconsistent

data (i.e., some dates and some text) then the field will be imported as a

text field.

4. If a user attempts to create a new custom attribute via API with a field name

that already exists in 15Five, the following error message will be returned

to the user: The attribute <insert attribute name> was not created because it

already exists.

5. This should include case-insensitive variations of the name.

6. When creating fields via API, the fields should be defaulted to all-lowercase

names.

7. If a user attempts to create via API more custom people attributes than their

company has room to support (i.e., they have attempted to upload 10

attributes and they already have 45 created on a limit of 50), the following

error message will be surfaced on the Bulk Import page: The number of

attributes exceeds the maximum limit (50 custom attributes).

8. If a user attempts to import text data for a field we know contains

date-based data, we will not update the data at all for that field and we

will surface the following error message: The data you attempted to import

(text) did not match the data currently associated with this field (dates).

No changes were made.