Verify Forms$FormSettings.TitleOverride: nil against Studio Pro BSON

[hjotha]

Source

Follow-up from ako's review on merged PR #338 (fix: write valid show-page parameter mappings).

Problem

PR #338 fixed `Forms$PageParameterMapping.Variable: nil` because Studio Pro rejected null embedded objects on project load. `Forms$FormSettings.TitleOverride` is written as `nil` in the same block (`sdk/mpr/writer_microflow_actions.go` around line 367). If TitleOverride is an embedded object, it needs the same empty-object treatment as Variable. If it is a string/expression scalar, `nil` is typically accepted.

Issue #295 (the reported bug) only mentioned Variable, so the current code may or may not cause a load failure depending on the Studio Pro version and the action context.

Expected behavior

`TitleOverride` in an authored MPR loads in Studio Pro without an "invalid project" error across all supported Mendix versions.

Proposed fix

1. Dump a Studio Pro-generated MPR with a show-page action and inspect the raw BSON for the TitleOverride field. Confirm type (scalar vs embedded object).
2. If embedded object: replace `nil` with an empty `Forms$TitleOverride` (or whatever the correct type is) document, mirroring `emptyPageVariable()`.
3. If scalar: add a code comment documenting that null is intentional and verified.
4. Add a regression test either way.

Related

• Reviewed in fix: write valid show-page parameter mappings #338 by ako.

[github-actions]

Issue Triage

Summary
The issue requests verification that the Forms$FormSettings.TitleOverride field is written (as nil or an empty object) so that Mendix Studio Pro can load the MPR without an “invalid project” error.

Checklist (bug‑report fields)

Required info	Present?	Notes
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	❌	No description of the command or MDL script being run
Expected output	⚠️	Described in words (“loads without error”) but not as a concrete expected result
Experienced output (error, wrong result, crash)	❌	Not provided
AI bug report (mxcli diag --bundle or session log)	❌	Not attached

What’s needed
To proceed, could you please add:

1. The version of mxcli you’re using (mxcli --version or commit/build info).
2. The Mendix version of the project you’re processing (e.g., 9.24, 10.6).
3. The exact scenario/command you ran that triggered the issue (e.g., mxcli mpr update …).
4. The exact error or behavior you observed (error message, crash, etc.).
5. If possible, the output of mxcli diag --bundle or at least the relevant session log.

Once those details are supplied, we’ll be able to investigate and verify the fix. Thanks for bringing this up!

---

Automated triage via OpenRouter — workflow source