Import inside the Domain Model the all the Actions and Entities from an Odata Consume Service

[acarum]

I'm not able to import the Entities ( NPE and External ) from Odata Consume Service ( like this https://services.odata.org/V4/TripPinServiceRW/$metadata) and the Actions available

[github-actions]

Issue Triage

Summary:
The user reports that mxcli cannot import entities and actions from an OData Consume Service into the domain model.

Checklist for bug report

Required info	Present?
mxcli version	❌
Mendix version	❌
Scenario (what they were trying to do)	❌
Expected output	❌
Experienced output (error/message)	❌
AI bug report (mxcli diag --bundle or session log)	❌

Comments:
To help investigate, could you please provide:

1. The version of mxcli you’re using (mxcli --version).
2. The Mendix version of the project (e.g., 10.6.0).
3. The exact command or MDL script you ran and what you expected to happen.
4. The actual result you saw (any error messages, wrong output, or crash).
5. If possible, run mxcli diag --bundle and share the generated log or bundle.

Thanks for reporting this—looking forward to getting the details needed to fix it!

---

Automated triage via OpenRouter — workflow source

[ako]

Progress update

We've implemented CREATE EXTERNAL ENTITIES FROM Module.Service on the odata branch, which bulk-creates external entities from a consumed OData service's cached $metadata. This addresses the entity import part of this issue.

Syntax

-- Import all entity types as external entities
CREATE EXTERNAL ENTITIES FROM Module.Service;

-- Import into a different module
CREATE EXTERNAL ENTITIES FROM Module.Service INTO TargetModule;

-- Filter to specific entities
CREATE EXTERNAL ENTITIES FROM Module.Service ENTITIES (Customer, Order);

-- Idempotent (updates existing)
CREATE OR MODIFY EXTERNAL ENTITIES FROM Module.Service;

External actions — proposal needs verification

For the action side (importing actions and their required complex types), we've written a design proposal that covers:

• Parsing <ComplexType> from $metadata (currently missing)
• Auto-creating non-persistent entities (NPEs) for complex action parameter/return types
• Response tree depth handling (how deep to deserialize the response object graph)

Before we can implement the action support, we need help verifying a few things:

1. Could you share an example project (or .mpr) that has a consumed OData service with actions that use complex types as parameters or return values? (e.g., TripPin's GetInvolvedPeople action)
2. When you configure a Call External Action in Studio Pro, do you see options for controlling response depth (top-level only vs. including associated objects)?
3. What's your primary use case — do you mainly need the entities from the contract, or are the actions equally important?

This will help us design the right solution. Thanks!

[acarum]

Are those capabilities available? Do I need to create another bug?
I used mxcli version v0.6.0-dirty (2026-04-09T16:08:35Z) with 11.9.0

But I’m getting an error

PROMPT: could you create External Entities from MyModule.TripPinServiceRW

The entities are available but not they are not External type