On a cloud site I’ve upgraded from 13 to 17, I’ve got a colour picker property basically just for colour visibility, not for doing anything and another one to pick a colour. Either of them doesn’t work with or without selecting a colour, and has the following validation error;
{type: "Error", title: "Validation failed", status: 400,…}
detail: "One or more properties did not pass validation"
errors: {,…}
$.values[13].value.contentData[1].values[3].value: ["The selected color '000000' is not one of the available options."]
0: "The selected color '000000' is not one of the available options."
operationStatus: "PropertyValidationError"
status: 400
title: "Validation failed"
type: "Error"
Did you find a solution to this? Im stuck with a massive site upgrade that even when i delete the affected content and try to recreate it i get this validationerror message
{"type":"Error","title":"Validation failed","status":400,"detail":"One or more properties did not pass validation","operationStatus":"PropertyValidationError","errors":{"$.values[9].value.settingsData[3].values[3].value":["\u0022The value \u0027lightlilac\u0027 is not one of the available options."]}}
obviously “lightlilac” is not a valid value for a color picker. It;s possible that the datatype was changed from a dropdown to a color pickerby a previous developer and “lightlilac” is an old value - but i have deleted out all the content blocks that use it and could possibly have the old value.
It looks like the value is still persist in the database and it’s preventing you to work. My issue was actually not colour picker in the end. Some other property was the issue and I had an odd mandatory field