MerginMaps / MerginMaps/mobile
`fid` field shown as empty instead of "* Mixed Values *" when editing multiple features
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Description
When editing multiple selected features, fields with differing values correctly display * Mixed Values * as a placeholder. However, the fid field (when visible in the form) is shown as empty rather than displaying * Mixed Values *, which is inconsistent with the behaviour of all other fields.
Environment
[ ] Staging [x] PROD
Application (+ app version, build, operating system)
- Mergin Maps mobile 2026.2.0, Android
- Mergin Maps mobile 2026.2.0, iOS
Steps to reproduce
- Open a project where the
fidfield is visible in the feature form (or create a new basic project withfidvisible) - Select multiple features on the map
- Tap Edit to open form for selected features**
- Observe the form fields
Actual results
The fid field is displayed as empty. All other fields with differing values correctly show * Mixed Values *, and unsupported fields (e.g. photo) show Not available while editing multiple features.
Expected results
The fid field should display * Mixed Values * consistently with all other fields that contain differing values across the selected features.
Screenshots or logs
Conclusion
Created by Claude and supervised by a human test analyst.
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
The issue does not identify a source file, test, or entry point. Reproduce the problem by editing multiple selected features with a visible fid field, then locate the form handling for mixed values and verify that fid displays "* Mixed Values *" consistently with other differing fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100