Importing entities into the Domain Model from an OData consumed service does not work properly.

[acarum]

Once you have imported the Entities from the https://services.odata.org/V4/TripPinServiceRW/$metadata service in the Domain Mode there are some errors

• Attribute '_Id' has max length 'unlimited' which is not the same as max length in the OData service which is '36'.
• Key cannot be empty
• 'Person' is marked Creatable=True in the OData service, but False in the app.
• Attribute 'UserName' of external entity 'Person' is not supported.
• 'Airport' is marked supports $top=True in the OData service, but False in the app.
• Key cannot be empty
• External entity 'PublicTransportations' is no longer readable in the OData service

mxcli version: internal build from commit e189a5c
Mendix version: 11.9
Expected output: no errors
Experienced output: some errors

[github-actions]

Issue Triage

Summary:
The user reports that importing entities from an OData service into the Mendix Domain Model produces validation errors (e.g., mismatched attribute lengths, missing keys, incorrect creatable/support flags).

Checklist of required bug‑report information

Required info	Present?	Details
mxcli version	✅	Internal build from commit e189a5cf40b8179bdbd14d71fdaf3aad3536f5b5
Mendix version	✅	11.9
Scenario (what was being done)	✅	Importing entities from https://services.odata.org/V4/TripPinServiceRW/$metadata in Domain Mode
Expected output	✅	No errors
Experienced output	✅	List of validation errors (see issue)
AI bug report (session log or mxcli diag --bundle)	❌	Not provided

Missing information:
To help diagnose the problem, could you please attach the session log or run mxcli diag --bundle and share the resulting archive? This will give us the internal details needed to investigate the import errors.

Thank you for reporting the issue!

---

Automated triage via OpenRouter — workflow source