Umbraoco Forms API number validation fails even when numerical value is provided

[tommhuth]

Which Umbraco version are you using?

version 13.5.3

Bug summary

Number validation fails even when numerical value is provided

Specifics

Forms API

Steps to reproduce

When submiting a form with the following (only) value

{"values": { "telefonnummer": 234234 } }

with telefonnummer set to field type number and required, the API POST gives a 422 error:

{
    "errors": {
        "telefonnummer": [
            "Venligst indtast en v\u00E6rdi for Telefonnummer"
        ]
    },
    "status": 422,
    "title": "One or more validation errors occurred."
}

If I change it to something else like text, the request goes through.

Expected result / actual result

Endpoint should not fail with valid data

[github-actions]

Hi there @tommhuth!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[tommhuth]

any movement on this? any reason this could be us? Its quite the akward blocker for the client, forcing number to be string instead as a workaround