Skip to content

Combo box bound to an association through the attribute key passes check, exec refuses #1440

Closed
ako/mxcli
#1376

Description

@MendixMau

Environment

  • mxcli: v0.26.0 (release binary, 2026-10-11)
  • Mendix app seen on: Mendix 9.24.2 / 10.24 / 11.12.0 / 11.13.0 test apps (FSM template, GenAI Showcase); version not pinned to one app in the report
  • OS: Linux x86_64 cloud container (no Studio Pro; mx/mxbuild only)

Summary

Combo box bound to an association through the attribute key passes check, exec refuses. Command / document type: alter snippet ... replace ... with { combobox }. Seen on: AssetsApp slice. — occurrences: 1

Reproduction

alter snippet M.S { replace <widget> with {
  combobox x (Attribute: $Asset.Asset_Customer, CaptionAttribute: CustomerManagement.Customer.CustomerName)
} };

Marketplace and project setup

Expected

check refuses.

Actual

check: Check passed!; exec: property attributeEnumeration binds Asset_Customer, which is an association ... not an attribute

only exec does (exec is correct).

Impact

usability, 1 occurrence(s) in the 2026-10-12 round-trip runs.

Activity

  1. github-actions commented on Oct 12, 2026

    @github-actions

    Issue Triage

    Summary:
    The mxcli check command incorrectly passes when a combobox is bound to an association via its attribute key, while mxcli exec correctly fails with an enumeration‑type error.

    Checklist (bug report)

    • ✅ mxcli version: v0.26.0 (release binary, 2026-10-11)
    • ✅ Mendix version(s): 9.24.2, 10.24, 11.12.0, 11.13.0 (tested)
    • ✅ Scenario: alter snippet … replace … with { combobox … } MDL script
    • ✅ Expected output: check should refuse (fail)
    • ✅ Experienced output: check passes; exec fails with “property attributeEnumeration binds Asset_Customer, which is an association … not an attribute”
    • ❌ AI bug report / session log (output of mxcli diag --bundle or at least the session log)

    Missing information:
    Could you please provide the session log or run mxcli diag --bundle and attach the resulting bundle? This will help us diagnose why the check phase is not catching the association‑type mismatch. Thank you!


    Automated triage via OpenRouter — workflow source

  2. added 2 commits that reference this issue on Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions