You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug or the crash? What were your expectations and what actually happened?
When a NULL value is set from an expression, the display of this value is 0 but is considered like a NULL value for other calculated fields. It appear with Shapefiles and Geopackages in the same way
Steps to reproduce the issue
_ Set a field with the checkbox tool (field1)
_ Set a field2 with a default value like : IF("field1" = 'False', NULL, "field2")
_ Enter a value in the field1
_ Change the value on 'False' in the field2
_ The value displayed for field1 should be 0 and not NULL (but considered as NULL)
Version
3.5.3-Fangorn
Operating system name
Android
Operating system version
Android 10 QP1A.190711.020
Reinstall QField
I have a fresh install of the latest QField version, but the problem persists.
Problem can be reliably reproduced, doesn't happen randomly.
Problem happens with all files and projects, not only some files or projects.
Additional context
No response
The text was updated successfully, but these errors were encountered:
What is the bug or the crash? What were your expectations and what actually happened?
When a NULL value is set from an expression, the display of this value is 0 but is considered like a NULL value for other calculated fields. It appear with Shapefiles and Geopackages in the same way
Steps to reproduce the issue
_ Set a field with the checkbox tool (field1)
_ Set a field2 with a default value like : IF("field1" = 'False', NULL, "field2")
_ Enter a value in the field1
_ Change the value on 'False' in the field2
_ The value displayed for field1 should be 0 and not NULL (but considered as NULL)
Version
3.5.3-Fangorn
Operating system name
Android
Operating system version
Android 10 QP1A.190711.020
Reinstall QField
Additional context
No response
The text was updated successfully, but these errors were encountered: