BUG: default_value is placebo

[mike_g]

This has been an issue for years. Both Select and Boolean types. When a new document is saved, a "null" value is returned. What's the point of a default value if staff has to jiggle the handle every time?

ex: I have a boolean field default set to true. When creating a new doc, the field states "true"... however after the doc is saved, the API returns "null" as a value for that field.
The work around: Toggle to "false"-- then toggle back to "true". Save

ex: I have a select field's default set to "blue". When creating a new doc, the field states "blue"... however after the doc is saved, the API returns "null" as a value for that field.
The work around: toggle to something else-- then back to "blue". Save.

What is the expected behavior when saving a new document after a default value in the content model has been defined?

[Pau]

Hello! there's a similar post related to this feature request. You can check it out here:

[Bug] Select & boolean fields return null rather than initial value

Hello, we're having an issue with some fields in slices created using Slice Machine. When we add a slice using the visual editor, many select and boolean fields have a default value, however when the new document is saved (leaving these default values selected and unchanged), the response from the Prismic API for these fields is null, rather than the default value (true/false, or the value in the select field). The only way to fix it is to select a different value, save the document, change it…