Support Topics Documentation Slack YouTube Blog

Validator is passable by changing case of variables

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

1.I make an object with firstName property being an empty string
2.I post a student object
3.I get a message that the validator failed

Actual Behavior

1.I make an object with firstName property being an empty string
2.I post a student object
3.The object is successfully created

The problem is that if I post the object with a FirstName property (which is the name in the database), the validator works correctly (it accepts anything other than an empty string). If I post it with FirstName with any of the characters in a different case, the object is created (with the invalid value). If I am missing the field, I get an error that the field does not have a default value. If I put something in the fiRStNamE field, it is saved. Is this a bug? Can I fix it so if someone tries to post a value to fiRStNamE, that value is validated?

Hello @Antonio_Skenderski,

I’ve created the internal ticket BKNDLSS-22243 to investigate this issue. We’ll give a response here as soon as possible.

Regards,
Olha

Hello @Antonio_Skenderski

We’ve just updated cloud servers with a fix for the issue you described above. Could you kindly let us know whether fix works for you well?

Regards,
Inna