SET caption is refering to first language, not default language

[jurretanjamx]

3. How to write the English caption? The CLI can't do it cleanly here: SET Caption wrote Dutch, and restating the snippet deleted the other languages.

• A (recommended): you change it in Studio Pro with the language set to English (United States). I then read back every language's text and run the gates.
• B: live edit through Studio Pro's MCP connection, which needs Studio Pro open with this project. It's untested for language handling, so I'd use mxcli diff first and read every language back after.

❯ No, you need to make the change for me, why aren't you able to do this for me in English?
You're right, I can do it in mxcli. First, the one-sentence answer: SET Caption has a bug where it writes the first stored translation instead of English, and restating the snippet writes English correctly but drops the other languages. There are two routes to check: whether mxcli can target a language directly, or a two-step fix where English is restated and the other three languages are put back with translation statements.

mxcli version v0.23.0
.mpr version 11.12.2

[github-actions]

Issue Triage

Summary:
The SET Caption command writes the first stored language translation instead of the default English and, when re‑applied, overwrites the caption in English while losing the other language translations.

Checklist

Required info	Present?	Notes
mxcli version	❌	Not provided
Mendix version	❌	Not provided
Scenario (what was tried)	✅	Mentioned use of SET Caption
Expected output	❌	Not explicitly stated
Experienced output	❌	Described behavior but no exact error/message
AI bug report (mxcli diag --bundle or session log)	❌	Not attached

What’s missing:
To investigate this bug, could you please add:

1. The output of mxcli --version (or the commit/build you’re using).
2. The Mendix version of the .mpr file you’re editing (e.g., 10.6, 9.24).
3. The exact mxcli command you ran (including any arguments).
4. A clear statement of what you expected to happen versus what actually happened (including any error messages).
5. If possible, run mxcli diag --bundle and share the resulting archive, or at least the session log from the command that failed.

Once we have those details we’ll be able to reproduce the issue and work on a fix. Thanks for reporting!

---

Automated triage via OpenRouter — workflow source