context: House number field are actually textfields, because there is no prefill tab on the number fields.
When this text field is prefilled with a int, it also submits this as a int which causes issues with the jsonschema's:
{"non_field_errors":["61 is not of type 'string'"]}
As a form designer i expect the data from this text field to be a string, regardless of what type the source data might be.
This would otherwise be impossible to map in the v2 objecttype.
Product versie / Product version
2.8.0
Customer reference
DH 708
Omschrijf het probleem / Describe the bug
context: House number field are actually textfields, because there is no prefill tab on the number fields.
When this text field is prefilled with a int, it also submits this as a int which causes issues with the jsonschema's: {"non_field_errors":["61 is not of type 'string'"]}
As a form designer i expect the data from this text field to be a string, regardless of what type the source data might be. This would otherwise be impossible to map in the v2 objecttype.