Time Profile Days/Hours Data Format

[GilbertCherrie]

When trying to post data to the Time Profile table the days and hours are being sent as strings where as the api expects symbols :days and :hours. This results in an error when creating a new time profile with a new react form. The days and hours selected on the react form are ignored and the time profile is created with all days and hours selected. Below is an image with the api request data. The second image is the result after the time profile is created and the third image is the result after the time profile is edited.

[Fryguy]

I think this is related to #17201, where the TimeProfile API is presenting the serialized profile column as Strings, but the backend is expecting Symbols. Some possible fixes to move forward

• Tactical fix: Change the API code to be aware of and write Symbols (or perhaps do this at the profile= method on the model).
• Medium term fix: Change the backend code to be aware of both Symbols or Strings, or just change the backend to only support Strings with a data migration for existing columns
• Long term fix: Get rid of the serialized column and use regular columns (perhaps Array columns) for the values, with a data migration. This may introduce backward compatibility issues, so we may need a temporary shim in the API.

[GilbertCherrie]

Another API issue, the API currently allows time profiles with duplicate names

[Fryguy]

Another API issue, the API currently allows time profiles with duplicate names

This is a model problem, IMO - there should probably be a validation on the model to not allow duplicates.