DESCRIBE ODATA SERVICE output not parseable — roundtrip broken

[retran]

Impact

DESCRIBE ODATA SERVICE emits MDL that fails to parse when re-executed as CREATE. Roundtrip workflow broken for published OData services.

Details

• DESCRIBE ODATA SERVICE emits publish entity ... expose (...) syntax.
• Parser rejects the expose block with bare as 'Name' (Key) syntax.
• OData clients and JSON structures roundtrip correctly; only published OData services broken.

Expected

DESCRIBE output is valid MDL accepted by the parser (roundtrip invariant).

---

Discovered during AI-assisted manual testing session (2026-04-29, mxcli v0.7.0-257-ga07e7e0).

[github-actions]

Issue Triage

Summary:
The DESCRIBE ODATA SERVICE command generates MDL that cannot be re‑used as a CREATE command because the produced expose block uses a syntax the parser rejects, breaking the round‑trip workflow for published OData services.

Checklist of required bug‑report information

Required info	Present?	Notes
mxcli version	✅	mxcli v0.7.0-257-ga07e7e0 provided
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	Described as running DESCRIBE ODATA SERVICE then attempting to reuse the output as a CREATE command
Expected output	✅	Valid MDL that the parser accepts (round‑trip invariant)
Experienced output	✅	Parser rejects the expose block with bare as 'Name' (Key) syntax
AI bug report (mxcli diag --bundle or session log)	❌	No diagnostic bundle or log attached

What’s missing:

• The Mendix version of the project you’re working with (e.g., 10.x, 9.x).
• A diagnostic bundle (mxcli diag --bundle) or at least the session log from the AI‑assisted test run.

Could you please add those details? Once we have them, we’ll be able to investigate the parsing issue more effectively. Thanks for reporting!

---

Automated triage via OpenRouter — workflow source