Skip to content

BUG_REPORT_mxcli_cross_module_entity_parameter.md

Latest commit

 

History

History
121 lines (90 loc) · 3.41 KB

BUG_REPORT_mxcli_cross_module_entity_parameter.md

File metadata and controls

121 lines (90 loc) · 3.41 KB

Bug Report: mxcli fails to create microflow with cross-module entity parameter

Summary

When creating a microflow with a parameter whose type is an entity from a different module (e.g., FeedbackModule.Feedback in a microflow in MyFirstModule), mxcli fails with a misleading error message.

Environment

  • mxcli version: Current (as of 2026-01-19)
  • Mendix version: 11.6.0
  • Platform: macOS (Darwin 25.2.0)

Steps to Reproduce

  1. Connect to a Mendix project:

    ./mxcli -p MesDemoApp.mpr

  2. Try to create a microflow with a cross-module entity parameter:

    CREATE MICROFLOW MyFirstModule.TestMicroflow (
  $Feedback: FeedbackModule.Feedback
)
RETURNS Boolean AS $IsValid
BEGIN
  DECLARE $IsValid Boolean = true;
  RETURN $IsValid;
END;
/

Expected Behavior

The microflow should be created with:

  • Parameter $Feedback of type FeedbackModule.Feedback
  • Return type Boolean

Actual Behavior

The command fails with the error:

Error: entity '.FeedbackModule' not found for parameter 'Feedback'

Additionally, parser warnings are shown:

line 2:27 mismatched input '.' expecting ')'

Analysis

The error message entity '.FeedbackModule' not found suggests the parser is incorrectly splitting the qualified entity name FeedbackModule.Feedback:

  • It appears to interpret FeedbackModule as .FeedbackModule (with a leading dot)
  • The entity name Feedback is being parsed separately

The parser seems to expect the parameter type to end at the module name, treating the . as an unexpected token.

Workaround Attempts

Attempt 1: Unqualified entity name

$Feedback: Feedback

Result: Microflow is created, but parameter type becomes Void instead of FeedbackModule.Feedback.

Attempt 2: Single-line command

./mxcli -p MesDemoApp.mpr -c "CREATE MICROFLOW MyFirstModule.TestParam(\$Feedback: FeedbackModule.Feedback) RETURNS Boolean AS \$IsValid BEGIN DECLARE \$IsValid Boolean = true; RETURN \$IsValid; END; /"

Result: Same error - entity '.FeedbackModule' not found

Attempt 3: Script file execution

./mxcli -p MesDemoApp.mpr -c "EXECUTE SCRIPT '/tmp/test.mdl'"

Result: Same error

Evidence

The mxcli check command reports syntax as valid:

Checking syntax: /tmp/val_feedback_simple.mdl
✓ Syntax OK (1 statements)

But execution still fails, indicating a disconnect between the syntax checker and the executor.

Comparison with Working Cases

Creating a microflow without entity parameters works fine:

CREATE MICROFLOW MyFirstModule.TestMicroflow()
RETURNS Boolean AS $IsValid
BEGIN
  DECLARE $IsValid Boolean = true;
  RETURN $IsValid;
END;
/

Result: Created microflow: MyFirstModule.TestMicroflow

Impact

This bug prevents using mxcli to create microflows that:

  • Accept entity parameters from other modules
  • Are common patterns like validation microflows (VAL_*) in custom modules that validate Marketplace module entities

Suggested Fix

The parameter type parser should correctly handle fully qualified entity names in the format Module.Entity. The . should be recognized as a namespace separator, not treated as an unexpected token.

Related

The skill documentation in .claude/skills/write-microflows.md shows the syntax:

-- Entity types
$Customer: Module.Entity

This confirms the intended syntax supports qualified entity names.