MerginMaps / MerginMaps/mobile
Value Relation Filter Not Applied Correctly for Dependent Fields
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Summary
-------------
When recording a feature (point) with a Value Relation field filtered by municipality (`"Píla"`), the OBEC field correctly returns 217 items for municipality `"Pila",` but the dependent ULICA field opens a popup window with empty rows (`"Píla"`) has no streets).
Project: Iva Testing / Ticket_4443
Applications:
-----------
Device/OS/APP: Samsung Galaxy A53 / Android 15 / MM 2026.3.0 - 824051
Device/OS/APP: IPhone 15 / iOS26.5 / MM 2026.3.0 - 918211
Steps to Reproduce
------------------------
1. Set up a Value Relation with a filter based on municipality `(e.g. "Pila")`.
2. Start recording a new feature (point).
3. Tap the OBEC field — observe the list of returned values (217 rows for `"Píla"`)
4. Tap the ULICA field — observe the popup window.
Actual Behavior
---------------------
- OBEC field correctly shows 217 items for "Pila". ✓
- ULICA field opens a popup window with empty rows — no data, no message.
Expected Behavior
------------------------
- OBEC field returns all records matching the filter for "Pila" (217 items) ✓
- ULICA field should either display an empty state with a message (e.g. "No items").
Screenrecord:
-------------------
https://github.com/user-attachments/assets/65d6a7b0-6308-492d-9485-919a496df7b3
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 or test is named. Start by reproducing the Value Relation flow on the listed Android or iOS versions, then trace the dependent ULICA field's popup behavior; done means an empty result displays a clear message such as "No items" instead of empty rows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100