We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
latest
No response
Having configured a ZGW APIs registration in the admin we get a confirmation code like OF-ASXGZE and the real registration fails.
We can see the ValidationError in the Submission's registration backend result:
ValidationError: {'product_url': [ErrorDetail(string='Dit veld mag niet leeg zijn.', code='blank')], 'zaaktype': [ErrorDetail(string='Dit veld mag niet leeg zijn.', code='blank')], 'informatieobjecttype': [ErrorDetail(string='Dit veld mag niet leeg zijn.', code='blank')]
None
The text was updated successfully, but these errors were encountered:
[#4899] Fixed optional serializer fields in ZaakOptionsSerializer
ec54837
Merge pull request #4903 from open-formulieren/fix/4899-validationerr…
e03dbbd
…or-in-zgw-registration [#4899] Fix optional serializer fields in ZaakOptionsSerializer
allow_blank=True
vaszig
Successfully merging a pull request may close this issue.
Product versie / Product version
latest
Customer reference
No response
Omschrijf het probleem / Describe the bug
Having configured a ZGW APIs registration in the admin we get a confirmation code like OF-ASXGZE and the real registration fails.
We can see the ValidationError in the Submission's registration backend result:
ValidationError: {'product_url': [ErrorDetail(string='Dit veld mag niet leeg zijn.', code='blank')], 'zaaktype': [ErrorDetail(string='Dit veld mag niet leeg zijn.', code='blank')], 'informatieobjecttype': [ErrorDetail(string='Dit veld mag niet leeg zijn.', code='blank')]
Stappen om te reproduceren / Steps to reproduce
Verwacht gedrag / Expected behavior
No response
Screen resolution
None
Device
None
OS
None
Browser
No response
The text was updated successfully, but these errors were encountered: