In the app editor, when I try to select a specific field value from a dropdown list that has multiple relationship fields pointing to the same collection (e.g., two fields both linking to a “Genders” collection, or two fields both linking to a “Levels” collection), clicking on the second/different option in the list does not select it — instead, the system saves the FIRST option in that list, regardless of which one I actually click.
Steps to reproduce:
1. Create two Relationship fields in a collection, both pointing to the same target collection (e.g. “Field A” and “Field B”, both → “Genders”)
2. In a Custom Filter or an Update action, try to select “Field B” from a dropdown that lists both fields
3. Result: the value shown/saved is “Field A” instead of “Field B”, even after clicking directly on “Field B”
4. This happens consistently across renamed fields, newly created fields, different browsers, and incognito mode — so it doesn’t seem to be a caching issue.
This is blocking me from configuring a reciprocal matching filter (comparing ‘what gender I’m looking for’ against ‘the other person’s gender’ in both directions)."
