MerginMaps / MerginMaps/mobile
expression like "CASE WHEN "other_column" = 'no' THEN NULL END" work on QGIS, block/lock column on MM
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Description
In a form in QGIS set the default value for a column as
CASE WHEN "other_column" = 'no' THEN NULL END
This works perfectly fine, if "other_column" value is set to "no" (in my case with a checkbox widget) then the content of the column where the default is applied is set/reset to NULL.
On the other hand on MM App this expression has the effect of blocking/locking the column, meaning that it turn as if was set to be not editable.
MM plugin 2026.3.0
MM App 2026.2.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified in the report. Reproduce the expression in MM App 2026.2.0 with the QGIS project and compare it with QGIS behavior; done means the column remains editable and is reset to NULL when other_column is set to 'no'.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp, ios
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100