Unable to create new Analysis Services due to validation requirements of UpperDetectionLimit and LowerDetectionLimit

[Perseus]

Steps to reproduce

Send a POST request to the analysisservice route to create a new Analysis Service with data in JSON format.

Current behavior

Validation fails, with the error message that the LDL and UDL fields expect a string but when I send a string, it expects an integer

Expected behavior

Analysis Service is succesfully created

Screenshot (optional)

[ramonski]

We need a specific fieldmanager for the FixedPointField here: https://github.com/senaite/senaite.jsonapi/blob/master/src/senaite/jsonapi/fieldmanagers.py

[aethelwulffe]

Hi, just wandered in to look into the status of this. I got no python under my belt, but I guess what I am hearing is that if you throw a value of one type, it returns an error saying it needs a different data type, and changes it's mind if you do the reverse, right? Solution being creating a class (archetype?) to handle the value and error checking of that specific defined field, as without, error checking defaults always results in an opposing error? Specificity being great if the field is often/always employed, but if otherwise, maybe a loose datatype check?
...Like I said, not a PY guy, just trying to be informed to answer the great level of anticipation and curiosity that LibreHealthIO/lh-ehr#1204 is generating, and will result in questions directed to me.