Hi @TakeshiOsanai
There's another way to enable null values. In the JSON definition you should have something like this:
{
"type": "object",
"properties": {
"days": {
"type": "integer"
}
}
}
In the example above we're indicating that "days" is a integer and only an integer. If it's something else it will fail. Since null is not an integer you get an error every time there's a null value.
To fix it you need to define that the value can receive 2 types. The actual type (string, integer, etc) and null. So you can do something like this:
{
"type": "object",
"properties": {
"days": {
"type": [
"integer",
"null"
]
}
}
}
Do this for all the types that you know that a null value is possible. Don't forget, in the Flow, to deal with the null values so not to save invalid values.
Now the type can be 2 things and not only one.
Does this make sense?
Can you please check if and let me know if you have any questions?
Cheers
Manuel
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
