Unchecked custom fields on keys do not return as "false" in web API.Answered

I'm testing a feature and noticed that with custom field checkboxes, that the Web API will not return it as a “false” value — it simply does not return the “name” / “value” as an object in the “feature” array.  Is that by design?

I would expect the feature to come back with a value of false or even 0 because when the checkbox is checked the value is coming back as `1`.

Should we just plan on coding around whether or not the feature is even present?

Hello!  Just bumping this up since it's been a while.  Can you confirm an answer to my question?

Answer

Hey Arie,

Yes, currently the web API returns the value if it's checked and doesn't return the value if it's unchecked.

We change it in the future. So, better to code to detect if the feature is present and set.

Reply
Discard post