When using a select field and checking the 'Define first value as default' option this returns null if not changed when creating the custom type. I was getting null for all types using the default value until I went into it, selected the second option, re-selected the first option and re-published. …

Hi David, Sorry, we missed this one. This has been fixed: [image] Default option in select field is not working Developing with Prismic It’s now partially deployed on production, please contact me in private message so we can activate the fix on your repository and make s…

Bug with select field

Prismic for Content Creators

Phil (Phil Snow) August 10, 2022, 3:12pm 11

Hi David,

Sorry, we missed this one. This has been fixed:

You can send me your repo name, and I can check if this has been fixed on your repo.

Thanks.

Topic		Replies	Views
BUG: default_value is placebo Developing with Prismic	1	265	July 28, 2023
BUG: Default value in select/bool fields not being set Developing with Prismic nextjs	1	615	April 6, 2022
[Bug] Select & boolean fields return null rather than initial value Developing with Prismic slice-machine , page-builder	27	2002	October 4, 2024
Prismic behaviour when adding new fields Developing with Prismic slice-machine	3	740	April 27, 2022
Select Field: Unable to clear a selected value after saving (even though “Define first value as default” is false) Prismic Administrative Support slice-machine , custom-types-api	3	11	October 21, 2024

Bug with select field

Related topics