'measured quantity' fields accept text string inputs without preserving all of them

Summary

When creating a 'measured quantity' for a device, all input fields accept text strings. The 'measured quantity' can be saved without an error message. However, when looking into the saved 'measured quantity' the fields "Failure Value", "Measuring range min", "Measuring range max", "Accuracy" and "Resolution" remain undefined, probably because a numeric value would have been expected.

Steps to reproduce

1. Create a new 'measured quantity' and fill each field with a text string.
2. Save the new measured quantity.
3. Look into the saved measured quantity and check if all inputs are saved.

What is the current bug behavior?

The text string inputs are accepted without any error message when saving the new 'measured quantity'. However, looking into the measured quantity afterwards shows that the fields "Failure Value", "Measuring range min", "Measuring range max", "Accuracy" and "Resolution" remain undefined. (see screenshots)

What is the expected correct behavior?

If text strings are invalid for certain fields there should be an error message latest as soon as the user tries to save.

Some logs and/or screenshots

Creation of new measured quantity with string 'test' in each field.

View of the created measured quantity showing empty fields.

Possible fixes

? tbd

ToDo's

• Bug reproduced
• Cause found
• Bug fixed