CREATE EXTERNAL ENTITIES FROM ODATA CLIENT syntax not implemented

[retran]

Description

The bulk import syntax CREATE EXTERNAL ENTITIES FROM ODATA CLIENT Module.ClientName produces a parse error. Only individual CREATE EXTERNAL ENTITY statements work.

Steps to Reproduce

./mxcli -p project.mpr -c "CREATE EXTERNAL ENTITIES FROM ODATA CLIENT LatoIntegrations.LatoODataClient"

Result: Parse error.

Expected

Bulk import of all entity sets from an OData client, or a clear "not implemented" error message.

Workaround

Create external entities individually:

CREATE EXTERNAL ENTITY Module.EntityName FROM ODATA CLIENT Module.Client (EntitySet: 'EntitySetName');

Severity

Medium — documented feature not available.

Reproducing test cases

• integration-test-cases.md § 19.1–19.4

[github-actions]

Issue Triage

Summary:
The user reports that the bulk import command CREATE EXTERNAL ENTITIES FROM ODATA CLIENT … fails with a parse error, while individual CREATE EXTERNAL ENTITY statements work.

Checklist (bug‑report fields)

Required info	Present?	Notes
mxcli version	❌	Not mentioned
Mendix version of the project	❌	Not mentioned
Scenario (what the user was trying to do)	✅	CLI command with MDL script shown
Expected output	✅	Bulk import of all entity sets or a clear “not implemented” message
Experienced output (exact error message, crash, etc.)	❌	Only “Parse error” is given; no full error output
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:
To help us investigate, could you please add:

1. The version of mxcli you’re running (mxcli --version or commit/build info).
2. The Mendix version of the .mpr project (e.g., 10.6.0, 9.24.1).
3. The exact error message or stack trace you see when the command fails.
4. If possible, run mxcli diag --bundle and attach the resulting bundle (or at least the session log).

Once we have those details, we’ll be able to reproduce the issue and work on a fix. Thank you for reporting this!

---

Automated triage via OpenRouter — workflow source