fix: SET $obj/Module.Assoc = $other rejected — isVariableDeclared does not handle path-style targets

[ako]

Bug

SET $obj/Module.Assoc = $other inside a microflow body fails validation with:

variable 'obj/Module.Assoc' is not declared

The in-CREATE form works fine:

create object $obj of MyModule.Order (
  MyModule.Order_Customer = $customer
);

Root cause

The grammar and parser both support association paths as SET targets (attributePath rule in MDLParser.g4). The parser captures the full path string obj/Module.Assoc into MfSetStmt.Target.

The failure is in isVariableDeclared (mdl/executor/cmd_microflows_builder.go), which does a direct map lookup using the full path string. Only the bare variable name obj is registered in varTypes. The function does not extract the variable prefix before looking up.

The fix: strip the path suffix (everything from the first / or .) before doing the map lookup in isVariableDeclared.

Reproduction

create microflow MyModule.ACT_LinkCustomer (
  $order: MyModule.Order,
  $customer: MyModule.Customer
)
begin
  -- This fails:
  set $order/MyModule.Order_Customer = $customer;
  return;
end;

Affected files

• mdl/executor/cmd_microflows_builder.go — isVariableDeclared function
• mdl/executor/cmd_microflows_builder_actions.go — call site (addChangeVariableAction)

Related

Also add a doctype test or bug test in mdl-examples/bug-tests/ covering this case so it doesn't regress.

[github-actions]

Issue Triage

Summary
The issue reports that using a path‑style target in a SET statement (e.g., SET $obj/Module.Assoc = $other) fails validation because isVariableDeclared looks up the full path instead of just the variable name.

Checklist of required bug‑report information

Required info	Present?	Details
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	MDL microflow with SET $order/MyModule.Order_Customer = $customer
Expected output	✅	The statement should succeed (as the in‑CREATE form does)
Experienced output (error message, crash, etc.)	✅	Validation error: variable 'obj/Module.Assoc' is not declared
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing
To help us reproduce and fix the problem, could you please add:

1. The version of mxcli you’re using (output of mxcli --version or the commit/build identifier).
2. The Mendix version of the project you’re processing (e.g., 10.6.0, 9.24.5).
3. If possible, a diagnostic bundle (mxcli diag --bundle) or at least the session log showing the validation failure.

Once we have those details, we’ll be able to verify the fix and add a regression test. Thanks for reporting this!

---

Automated triage via OpenRouter — workflow source