<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vishnu Prasath T A on Medium]]></title>
        <description><![CDATA[Stories by Vishnu Prasath T A on Medium]]></description>
        <link>https://medium.com/@vishnuprasath011?source=rss-13c8b5bcfec7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9j6TMbqMA1zaFC5PC5V-hg.jpeg</url>
            <title>Stories by Vishnu Prasath T A on Medium</title>
            <link>https://medium.com/@vishnuprasath011?source=rss-13c8b5bcfec7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:16:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vishnuprasath011/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Meet Concord: mxcli’s Cooler Cousin]]></title>
            <link>https://medium.com/mendix/meet-concord-mxclis-cooler-cousin-a6d55d17cca9?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6d55d17cca9</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mcp-server]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 05:13:31 GMT</pubDate>
            <atom:updated>2026-11-11T05:13:31.784Z</atom:updated>
            <content:encoded><![CDATA[<p>What if your AI agent could work <em>inside</em> Mendix Studio Pro, while you watch every change appear? That is <strong>Concord</strong>.</p><p>This is the short tour: what it is, how it differs from mxcli, how to set it up, and where it falls short.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*862jQCPxL1H8EJbX_2fMPA.jpeg" /><figcaption>mxcli vs concord</figcaption></figure><h3>What is Concord?</h3><p>Concord is a Studio Pro extension from the Mendix CoE team. It docks a terminal inside Studio Pro and runs the AI coding agent you already use: Claude Code, Codex, or GitHub Copilot CLI.</p><p>Why it matters: a Mendix app is not a folder of code. The model lives inside Studio Pro, so a normal agent cannot reach it. Think of a mechanic who finally gets to open the hood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Goka3ggGV8lrvSa_-SDQug.png" /></figure><p><strong>What can it do?</strong></p><ul><li><strong>Explain</strong> any microflow, page or entity</li><li><strong>Build</strong> entities, attributes, microflows and pages</li><li><strong>Turn a screenshot or HTML prototype</strong> into Mendix pages</li><li><strong>Run the app and fix</strong> build errors</li><li><strong>Help with security and upgrades</strong></li></ul><p>You bring your own signed-in CLI. Concord adds no subscription and no API key of its own.</p><h3>Concord vs mxcli</h3><p>The core difference: <strong>mxcli edits your project files while Studio Pro is closed. Concord works inside Studio Pro while it is open.</strong></p><p>Think of Word. mxcli is editing the raw file with another tool while Word is shut. Concord is a colleague using Word itself while you watch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*bIBxMrAJkOaPUc9K_UOJ1Q.png" /></figure><p><strong>Pick mxcli when you need</strong></p><ul><li>Scripts, CI or other headless jobs</li><li>Repeatable bulk changes (a command beats a chat prompt)</li><li>Support for Studio Pro versions older than 11.10</li></ul><p><strong>Pick Concord when you want</strong></p><ul><li>A live, interactive loop with no close, edit, reopen cycle</li><li>Plain English instead of command syntax</li><li>Changes you can review and undo in the normal editors</li><li>Run, read the errors, fix, repeat</li></ul><p>They are not rivals. Use both.</p><h3>Setup in 5 steps</h3><ol><li><strong>Check your version.</strong> Studio Pro 11.10 to 11.16, on Windows x64 or macOS.</li><li><strong>Turn on the MCP server.</strong> In Edit &gt; Preferences, enable the MCP Server (under the Maia or AI section) and pick a free port.</li><li><strong>Install Concord</strong> from the Mendix Marketplace and enable Extension Development.</li><li><strong>Open it once, then restart.</strong> Go to Extensions &gt; Concord &gt; Open Concord2 Terminal, then close Studio Pro completely and reopen it.</li><li><strong>Run Setup Status.</strong> In the Concord pane: Settings gear &gt; View setup status &gt; Run status check. Use the Fix button if it offers one.</li></ol><p>Sign in to your CLI first, and commit or back up your app before the first prompt.</p><h3>Limitations</h3><ul><li><strong>Not everything is covered.</strong> Concord can only do what Studio Pro’s MCP server exposes. Nanoflows and rules are not supported yet.</li><li><strong>Some automation is Windows-only,</strong> such as reading the Errors pane and auto-run. On macOS you press Run yourself.</li><li><strong>Version window.</strong> Studio Pro 11.10 to 11.16 only. No 10.x.</li><li><strong>Self-supported.</strong> Concord is supported by the Mendix CoE team, not by Mendix Product Support.</li><li><strong>Safety rules are instructions.</strong> Agents are told never to commit or push, but your CLI’s approval settings are what enforce it. Review every change like a pull request.</li></ul><h3>The bottom line</h3><p>Concord does not replace your whole toolbox yet. But for everyday interactive building, an agent that works where your model lives is a big step. Keep mxcli for the scripted jobs.</p><p><em>Sources: the Mendix blog post “</em><a href="https://www.mendix.com/blog/bring-your-own-agent-to-studio-pro-meet-concord/"><em>Bring Your Own Agent to Studio Pro: Meet Concord</em></a><em>” and the Studio Pro MCP Server documentation.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6d55d17cca9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/meet-concord-mxclis-cooler-cousin-a6d55d17cca9">Meet Concord: mxcli’s Cooler Cousin</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fire and Forget: Why Mendix Needed a Broker]]></title>
            <link>https://medium.com/mendix/fire-and-forget-why-mendix-needed-a-broker-49693fcb5b7b?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/49693fcb5b7b</guid>
            <category><![CDATA[business-event]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[tips]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 07:45:23 GMT</pubDate>
            <atom:updated>2026-10-13T11:20:27.350Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Fire and Forget: Why Mendix Needed a Broker (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*BRSykB39eiFYytILt7yo6g.png" /><figcaption>Fire and Forget: Why Mendix Needed a Broker</figcaption></figure><h4>Three ways to get one app to tell another app something happened. They are not interchangeable.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0aNYGJMRga9-QsEZbReZQ.png" /></figure><h3>The scenario</h3><p>An <strong>e-commerce platform</strong> cancels an order. Three other systems need to know:</p><ul><li><strong>Shipping</strong> — stop the shipment</li><li><strong>Notifications</strong> — email the customer</li><li><strong>Analytics</strong> — log the cancellation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1NNiPNQEW8YgAh2DwXlpDw.jpeg" /></figure><h3>Option 1 — API calls</h3><pre>Order app → POST /shipping/cancel      → waits for 200 OK<br>Order app → POST /notifications/send   → waits for 200 OK<br>Order app → POST /analytics/log        → waits for 200 OK</pre><p><strong>Example:</strong> the Order app’s cancellation microflow calls three REST endpoints, one after another, each with the order ID in the request body. If the Notifications service is mid-deploy and returns a 503, the whole cancellation flow either fails or has to retry that one call — while the customer is sitting on a “cancelling your order…” spinner.</p><ul><li>Order app must know all three endpoints, by name, in advance</li><li>All three must be online <strong>right now</strong></li><li>Add a Refunds service later → go edit the Order app’s cancellation microflow</li><li>One slow responder → the whole chain slows down</li></ul><p><strong>Tightly coupled. Synchronous. Fragile at scale.</strong></p><h3>Option 2 — RabbitMQ</h3><pre>Order app → publishes to &quot;order_exchange&quot;<br>             routing key: &quot;order.cancelled&quot;<br>             payload: {&quot;orderId&quot;: &quot;4471&quot;, &quot;reason&quot;: &quot;customer_request&quot;}</pre><p><strong>Example:</strong> the Order app publishes once to the exchange, with that routing key. A shipping_queue and a notifications_queue are both bound to order.cancelled. Both receive a copy. If the Notifications service happens to be down for maintenance, the message just sits in notifications_queue — nothing is lost, nothing retries on the Order app&#39;s side, and the Order app already moved on the moment it published.</p><ul><li>Order app doesn’t know who’s listening, or how many</li><li>Consumers subscribe independently, by binding a queue to the exchange</li><li>Add a Refunds consumer later → bind a new queue with the same routing key. Order app’s code: untouched</li><li>A down consumer doesn’t block the publisher — the message just waits</li></ul><p><strong>Loosely coupled. Fire-and-forget. The broker is self-hosted.</strong></p><h3>Option 3 — Mendix Business Events</h3><pre>Order app → &quot;Publish business event&quot;<br>             Subject: &quot;Order cancelled&quot;<br>             Event data: $CancelledOrder (orderId, reason)<br>             → Mendix Event Broker → subscriber apps</pre><p><strong>Example:</strong> a Shipping app, built separately in Mendix, subscribes to the OrderCancelled event. Mendix auto-generates a Handle_BE_OrderCancelled microflow in that app. The moment the Order app&#39;s microflow publishes and commits successfully, the Shipping app&#39;s handler fires — no polling, no manual &quot;check if anything&#39;s new&quot; step on either side.</p><ul><li>Same loose-coupling idea as RabbitMQ, without touching Java or Docker</li><li>Subscriber microflows fire <strong>automatically</strong> the instant the event lands</li><li>Publishing rolls back automatically if the publishing microflow’s transaction fails</li></ul><p><strong>Loosely coupled and Push-based. Mendix runs the broker.</strong></p><h3>The catch with Business Events</h3><ul><li><strong>Mendix apps only.</strong> A non-Mendix system — a Java backend, a .NET service, a third-party SaaS webhook — cannot publish directly into it.</li><li><strong>Needs a paid Event Broker license</strong> to run in Mendix Cloud production.</li><li><strong>No self-hosting option</strong> for the broker piece — the infrastructure is Mendix’s, not the developer’s.</li></ul><h3>Side by side</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EJlcbkGgZ3l-w_gXPlorMw.jpeg" /></figure><h3>Which one, when</h3><ul><li><strong>API call</strong> — a response is genuinely needed back, right now, from one specific system</li><li><strong>RabbitMQ</strong> — external or non-Mendix systems are involved, or the broker needs to be self-hosted</li><li><strong>Business Events</strong> — pure Mendix-to-Mendix, with no interest in building or running broker infrastructure</li></ul><h4>Read More</h4><p><a href="https://docs.mendix.com/appstore/services/event-broker/">Mendix Event Broker</a></p><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49693fcb5b7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/fire-and-forget-why-mendix-needed-a-broker-49693fcb5b7b">Fire and Forget: Why Mendix Needed a Broker</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix in Docker, One Command]]></title>
            <link>https://medium.com/mendix/mendix-in-docker-one-command-781154324dc6?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/781154324dc6</guid>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[tips]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 04:31:03 GMT</pubDate>
            <atom:updated>2026-10-02T11:44:17.422Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Mendix in Docker, One Command (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*G_F-LBOoGrDjHtaYVum8Gw.png" /><figcaption>Mendix in Docker, One Command</figcaption></figure><h3>How One npm Command (And a Lot of Stubborn Debugging) Turned My Terminal Into a Headless Mendix Studio</h3><h3>The itch 🤔</h3><p>If you’ve used Mendix, you know Studio Pro — the big, friendly visual editor where you click your way to an app. It’s great. But it’s also a <em>window you have to open</em>, a GUI you have to drive by hand.</p><p>I had a different idea:</p><blockquote><em>What if my AI assistant could build, check, and run a Mendix app entirely from the command line — and I never had to open Studio Pro at all?</em></blockquote><p><strong><em>Spoiler:</em></strong> it can. And the journey to get there was equal parts “wow, this actually works” and “why is this build hanging for 39 minutes?” 😅</p><p>Grab a coffee — this one’s a ride!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVQproiQL7qvEc5crTpQiA.png" /><figcaption>npx mx-studio-automate</figcaption></figure><h3>First, a myth to bust 🧨</h3><p>When people hear “Mendix without Studio Pro,” they assume I’m <em>faking</em> or <em>emulating</em> Mendix. Nope.</p><p>Studio Pro is really just a dashboard wrapped around real engines:</p><ul><li>🖱️ Click in the domain model / pages → the model engine that reads &amp; writes the .mpr</li><li>🔴 See red error markers → mxbuild / mx check</li><li>▶️ Hit Run Locally → builds the app + spins up a runtime + a database</li></ul><p>My setup just drives those same engines from the terminal — the <em>real</em> mxbuild.exe, the <em>real</em> Mendix runtime. Two steering wheels, one engine.</p><blockquote><em>“It’s not a simulator. It’s the same Mendix machinery — just headless.”</em></blockquote><h3>The cast of characters 🎭</h3><p>To go GUI-free, my AI agent needs four tools working together:</p><ul><li>🛠️ mxcli — edits the Mendix model from the command line</li><li>🔎 mxbuild — the error checker (same one Studio Pro uses)</li><li>🐳 Docker — runs the app + a Postgres database in containers</li><li>🔬 Chrome DevTools — lets the agent verify the running UI</li></ul><p>The problem? Setting all of that up by hand, on a fresh machine, is a <em>chore</em>. So I packaged it.</p><h3>Enter: mx-studio-automate ✨</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ak0QybQBfB_RXTUGpLVmUg.png" /><figcaption>One command checks (and fixes) your whole environment.</figcaption></figure><p>One command:</p><pre>npx mx-studio-automate</pre><p>It scans your machine, auto-installs the safe stuff, and gives you copy-paste instructions for the heavy stuff (like Docker, which needs admin rights). It even wires up the AI agent’s config so it’s ready immediately.</p><pre>mx-studio-automate  v0.3.0<br>✔  mxcli            found   v1.4.0<br>✔  mxbuild          found   11.10.0<br>✔  JDK 21           found   21.0.11<br>✔  Docker           found   29.3.1<br>✔  Chrome DevTools  found<br>✔  AI agent config  found<br>🎉  All set!</pre><p>Safe to re-run any time — it only ever fills the gaps.</p><blockquote><em>❓ Reader check: How long does setting up a new dev environment usually take you — minutes, or a “clear your afternoon” kind of thing? 👇</em></blockquote><h3>The headline trick: build and run, no Studio Pro 🚀</h3><pre>npx mx-studio-automate --run</pre><p>Behind the scenes it does the whole Mendix deployment dance:</p><ol><li>Generates a Docker stack (app + Postgres)</li><li>Builds the app package with mxbuild</li><li>Boots it all in Docker</li><li>Hands you a live URL</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IzL2PSvwJaOj77pVkH5vaQ.png" /><figcaption>A real Mendix app, running in Docker, launched from one terminal command.</figcaption></figure><p>And because builds can be slow and silent, I added a live loader so you always know it’s alive (and won’t rage-quit mid-build):</p><pre>⠹  Building app package… 1m 12s — please don&#39;t close this window</pre><p>Then, for the edit→see loop, there’s --reload — a hot reload that pushes your changes into the <em>already-running</em> app in seconds, no cold restart:</p><pre>npx mx-studio-automate --reload          # rebuild + reload<br>npx mx-studio-automate --reload --css    # styling only, instant</pre><blockquote><em>💡 Tip: After the first </em><em>--run, you never cold-start again. Edit → </em><em>--reload → refresh browser. That&#39;s the whole loop.</em></blockquote><h3>A little terminal eye-candy 🎨</h3><p>Because if you’re going to stare at a CLI all day, it might as well be pretty. The intro draws itself in — mx as a faint outline, studio in crisp white, automate in Mendix blue:</p><pre> _ __ ___ __  __<br>| &#39;_ ` _ \ \/ /<br>| | | | | |&gt;  &lt;<br>|_| |_| |_/_/\_\<br>    _             _  _<br> ___| |_ _   _  __| (_) ___<br>/ __| __| | | |/ _` | |/ _ \<br>\__ \ |_| |_| | (_| | | (_) |<br>|___/\__|\__,_|\__,_|_|\___/<br>             _                        _<br>  __ _ _   _| |_ ___  _ __ ___   __ _| |_ ___<br> / _` | | | | __/ _ \| &#39;_ ` _ \ / _` | __/ _ \<br>| (_| | |_| | || (_) | | | | | | (_| | ||  __/<br>\__,_|\__,_|\__\___/|_| |_| |_|\__,_|\__\___|</pre><blockquote><em>🎬 GIF — Record the intro animation (mx → studio → automate revealing top-to-bottom) and drop a short looping GIF here. Tools: ScreenToGif (Windows) / Kap (macOS). </em>Caption:<em> “Yes, I spent an embarrassing amount of time on a terminal banner. Worth it.”</em></blockquote><h3>So… should you use it? 🧭</h3><p>If you’re a Mendix developer who:</p><ul><li>💻 lives in the terminal,</li><li>🤖 wants an AI agent to drive your project,</li><li>🐳 likes running apps in Docker, and</li><li>🙅 would rather not open a heavy IDE just to check for errors —</li></ul><p>…then give it a spin:</p><pre>npx mx-studio-automate</pre><p>It’s open source, MIT-licensed, and on npm. ⭐</p><h3>What I learned 📚</h3><ul><li>The “magic” of low-code tools is just real tooling with a nice UI — and you can absolutely reach the tooling directly.</li><li>A good CLI is honest: do the safe magic, but tell the user clearly when <em>they</em> need to act.</li><li>Half of shipping a dev tool is debugging other people’s environments — spaces in paths, stale cookies, version twins, hidden prompts.</li><li>And a little terminal polish goes a long way. 💙</li></ul><h3>👋 Your turn</h3><p>Have you ever ditched a GUI for the command line and never looked back? Or is there a tool you wish had a headless mode? Drop it in the responses — I read every one.</p><p><em>If this was useful, a few 👏 claps help more people find it. Thanks for reading!</em></p><p>Read more</p><ul><li><a href="https://docs.mendix.com/developerportal/deploy/docker-deploy/">Docker Buildpack</a></li><li><a href="https://docs.mendix.com/developerportal/deploy/docker-deploy-pad/">Reference Guide for Docker Deployment</a></li></ul><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=781154324dc6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/mendix-in-docker-one-command-781154324dc6">Mendix in Docker, One Command🐳</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your .mpr Just Learned English.]]></title>
            <link>https://medium.com/mendix/your-mpr-just-learned-english-6b14120659c2?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b14120659c2</guid>
            <category><![CDATA[mdl]]></category>
            <category><![CDATA[mendix-developer]]></category>
            <category><![CDATA[mxcli]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Wed, 06 May 2026 07:53:05 GMT</pubDate>
            <atom:updated>2026-08-17T17:30:54.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WwyM38C-hl1f1_CkWQ38sg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0-1AxJrbA5J2MPN_bq487Q.png" /></figure><h3>A coffee-break update on mxcli — what’s actually in the repo today, what just shipped in v0.8.0, and what still wants to bite your .mpr file.</h3><p>A few months ago I wrote a not-very-flattering blog about mxcli. It returned zero microflows from a real project, and the README warned it could corrupt my project file. I called it a chainsaw with “may occasionally explode” written on the handle.</p><p>Reader, I stand by every word. <em>And</em> I went back to look at the repo this week — <strong>v0.8.0 dropped yesterday</strong> — and it turns out the chainsaw has grown a brain.</p><h3>The thing I did not see coming</h3><p>Brace yourself. This is real Mendix, written into a real .mdl file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k8uNNfP76z45kTQmH0LLEg.png" /></figure><p>Yes. That is MDL — Mendix Definition Language — and it’s a SQL-flavoured way to read, query, and write to your Mendix project from a text file. The repo describes it as “<em>a SQL-like syntax for querying and modifying Mendix models</em>”, and it is exactly that. CREATE ENTITY. CREATE ASSOCIATION. GRANT VIEW ON PAGE. SHOW CALLERS OF ... TRANSITIVE.</p><p>If you’re a Mendix dev, your brain is doing the thing right now. I had to read it three times.</p><h3>Why this exists</h3><p>Mendix projects are stored as .mpr files — basically a SQLite database wearing a trench coat full of binary blobs. AI agents (Claude Code, Cursor, Continue, Windsurf, Aider, GitHub Copilot, OpenCode) cannot read that. Studio Pro can, but Studio Pro doesn&#39;t take instructions from a text prompt.</p><p>mxcli sits in the middle and translates:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3A8DerueyCG-_p2NoG-DJw.png" /></figure><p>Suddenly your AI assistant has a way to read your project, navigate it, and (carefully) modify it.</p><h3>What’s actually in the repo right now</h3><p>This is the part I want you to know is <em>real</em>, not roadmap. Pulled from the README and the docs site this week:</p><ul><li><strong>MDL command-line and REPL.</strong> Like psql but for your Mendix project. SHOW MODULES; DESCRIBE PAGE Sales.Customer_Edit; Plus SHOW STRUCTURE for a full project overview.</li><li><strong>mxcli new MyApp --version 11.8.0.</strong> One command spins up a fresh Mendix project, downloads MxBuild, generates the AI tooling (.claude/, AGENTS.md, skills) and a Dev Container — open it in VS Code, click &quot;Reopen in Container&quot;, you&#39;re going. This is wild.</li><li><strong>Catalog queries — proper SQL on project metadata.</strong> Tables called MICROFLOWS, ENTITIES, WIDGETS, REFS, STRINGS, ACTIVITIES. Find every microflow with more than 10 activities in one query.</li><li><strong>Code navigation.</strong> mxcli callers, mxcli refs, mxcli impact, mxcli context --depth 3. Impact analysis on your domain model from a terminal.</li><li><strong>Linter.</strong> 14 built-in Go rules + 27 Starlark rules covering security, architecture, quality, naming, and Mendix conventions. SARIF output for CI.</li><li><strong>Best-practices report.</strong> 0–100 scored across 6 categories, exportable as Markdown, HTML, or JSON.</li><li><strong>OData support in MDL.</strong> CREATE ODATA CLIENT, CREATE ODATA SERVICE with PUBLISH ENTITY blocks. Full control flow too — IF/THEN/ELSE, LOOP, WHILE, CASE, TRY/CATCH, ON ERROR.</li><li><strong>Multi-tool support out of the box.</strong> mxcli init configures Claude Code, Cursor, Continue.dev, Windsurf, Aider, GitHub Copilot, or OpenCode. Each gets its own config files.</li><li><strong>VS Code MDL extension.</strong> Syntax highlighting, hover, go-to-definition, code completion for .mdl files. Auto-installed by mxcli init.</li><li><strong>Zero-install Playground.</strong> A separate mxcli-playground repo lets you open mxcli in GitHub Codespaces with a sample Mendix 11.x project, JDK, Docker-in-Docker, and Claude Code already wired up. No local install required.</li></ul><p>Honestly: of the things I criticised six months ago, most have been solved.</p><h3>What v0.8.0 means</h3><p>Full disclosure — when I wrote this, GitHub was rate-limiting me and I couldn’t pull the exact v0.8.0 release-notes page. Go click through; it’s worth a read. What I <em>can</em> tell you, from the README and docs that are live this week, is that the current state of the tool is dramatically more capable than v0.2.0 was two months ago. Recent commit activity shows movement on workflow microflow actions, context hints in DESCRIBE PAGE, association navigation fixes, REST request body handling, and a typed error system for the executor. Whether all of that is in v0.8.0 specifically or spread across the recent minor versions, the trajectory is clear.</p><p>The takeaway: this is a project that’s shipping fast. v0.2.0 was alpha with thin coverage. v0.8.0 reads like something you can actually use on a Mendix 11.6 project today.</p><h3>Now the part that hasn’t changed</h3><p>The README still opens with this banner, and I quote with affection:</p><blockquote><strong><em>WARNING: Alpha-quality software.</em></strong><em> This project is in early stages and has been largely vibe-engineered with AI coding assistants. Expect bugs, missing features, and rough edges. </em><strong><em>mxcli can corrupt your Mendix project files</em></strong><em> — always work on a copy or use version control.</em></blockquote><p>“Largely vibe-engineered with AI coding assistants” is <em>the most honest disclaimer in software</em>. Frame that. Print it on a t-shirt.</p><p>A few specifics worth tattooing on your forearm before you use this thing:</p><ul><li><strong>It’s only validated against Mendix 11.6.</strong> Other versions (8.x through 11.x) are claimed to work but the docs are honest about what’s actually been tested.</li><li><strong>Don’t run mxcli on a project that’s open in Studio Pro.</strong> Studio Pro keeps in-memory caches and will overwrite your changes when it saves. Close the project, run mxcli, then reopen.</li><li><strong>Widget bulk updates (</strong><strong>UPDATE WIDGETS SET ...) are flagged as an &quot;untested proof-of-concept&quot;.</strong> Always DRY RUN first. Always.</li><li><strong>Anything that writes to your project gets the same disclaimer.</strong> Use a copy. Use version control. Use both, ideally.</li></ul><h3>Should you use it?</h3><p>For <em>reading</em> your project — searching, listing, describing, linting, generating reports? Absolutely. It’s effectively risk-free and immediately useful, especially in CI.</p><p>For <em>writing</em> to your project? Only ever on a copy or with version control on a tight leash. The README is not exaggerating — and if you blow up your .mpr, no amount of clever AI prompting brings it back.</p><p>For <em>AI agents writing code into your Mendix project autonomously</em>? That’s the actual frontier mxcli is building toward. With v0.8.0, it’s getting close enough to actually try. The Playground gives you a zero-risk way to start.</p><h3>The takeaway</h3><p>mxcli at v0.8.0 is genuinely impressive for what it is — a small, alpha-quality, vibe-engineered tool that just happens to be the only thing standing between Mendix’s binary .mpr format and the entire AI-assisted-coding ecosystem. The fact that it works at all is remarkable. The fact that you can write CREATE ENTITY in a text file and have it actually create an entity in your Mendix project is, frankly, slightly suspicious.</p><p>I’m cautiously optimistic. I’m also working on a copy.</p><blockquote><em>Star the repo. Try it on a backup. Don’t blame me if it eats your project.</em></blockquote><p>github.com/mendixlabs/mxcli</p><p><em>Have you used mxcli yet? Found a way to wire it into your CI? Broken something interesting with it? Drop a comment — the war stories are how we all figure this thing out.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b14120659c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/your-mpr-just-learned-english-6b14120659c2">Your .mpr Just Learned English.</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Rollback, It’s Over. Signed, mx-error-handler]]></title>
            <link>https://medium.com/mendix/dear-rollback-its-over-signed-mx-error-handler-5f2daee76a6d?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f2daee76a6d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[error-handling]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Sat, 18 Apr 2026 09:41:16 GMT</pubDate>
            <atom:updated>2026-09-11T18:19:25.355Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOvF0a0eELOb7-2dwwXAYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnEWjTDz-ExJo363ErlIPw.png" /></figure><p><em>A love letter to automation. And a breakup letter to manual error handling.</em></p><h3>The crime scene 🔍</h3><p>Picture this.</p><p>Sprint deadline in two days. Your Mendix module has 30 microflows. Every single REST call, Java action, and sub-microflow is sitting on the default Rollback error handling.</p><p>You know what Rollback does when something fails in production?</p><p><em>Nothing. Absolutely nothing. Just silently eats the error like it never happened.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/0*98rRJDXZ8iKE-DL5.jpg" /></figure><p><em>UAT. Production. Doesn’t matter. Rollback says: not my problem.</em></p><h3>What “Manual Error Handling” actually looks like</h3><p>Open microflow → find activity → right-click → configure error handling → type log expression → close → next microflow.</p><p><strong>Thirty times.</strong></p><p>And then your colleague opens a different module and writes:</p><pre>&#39;error: &#39; + $latestError/Message</pre><p>And you wrote:</p><pre>&#39;[ERR] &#39; + $latestError/ErrorType + &#39; | &#39; + $latestError/Message</pre><p>And your senior wrote something nobody can read.</p><p>Three developers. Three formats. Zero consistency. One very confused support team at 2am.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*l-wSxhze4g_vgu-A.jpg" /></figure><p><em>Day three of manual error handling. He is not okay.</em></p><h3>So I built mx-error-handler 🛠️</h3><p>One command. Whole module. Done.</p><pre>mx-error-handler patch --module IntegrationLayer --project &quot;App.mpr&quot;</pre><p>That’s it. Close Studio Pro, run that, open Studio Pro again. Every Java action, REST call, JS action, and sub-microflow call in that module now has a proper custom error handler with a standardised log message.</p><p>Go make a coffee. You’ve earned it. ☕</p><h3>How it works (the non-boring version)</h3><p>Under the hood, mx-error-handler uses mxcli + MDL commands (Mendix Definition Language) to modify your .mpr file directly — the same way mxcli reads and writes Mendix models.</p><p>Think of it as a developer who never gets tired of clicking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*S-YAd5bdeIWKlv0z.jpg" /></figure><p><em>mx-error-handler, clocking in for its shift.</em></p><p>Before touching anything, it:</p><ol><li>Writes a safety snapshot of your .mpr</li><li>Validates every MDL replacement before applying it</li><li>Skips anything it’s not confident about (more on this below)</li><li>Logs everything it touched so you know exactly what changed</li></ol><h3>The four commands you actually need</h3><p><strong>See what needs fixing — zero file changes:</strong></p><pre>mx-error-handler audit --module IntegrationLayer --project &quot;App.mpr&quot;</pre><p><strong>Preview before committing:</strong></p><pre>mx-error-handler patch --module IntegrationLayer --dry-run --project &quot;App.mpr&quot;</pre><p><strong>Apply it:</strong></p><pre>mx-error-handler patch --module IntegrationLayer --project &quot;App.mpr&quot;</pre><p><strong>Something looks wrong? Roll back instantly:</strong></p><pre>mx-error-handler restore &lt;snapshot-path&gt; --project &quot;App.mpr&quot;</pre><p>Always audit first. Always dry-run second. Always verify in Studio Pro before anything else. This is the way. 🙏</p><h3>Team-wide log format: mx-error-handler.json 🎯</h3><p>Here’s the part your whole team will actually thank you for.</p><p>Drop one file next to App.mpr:</p><pre>{<br>  &quot;templates&quot;: {<br>    &quot;apiflow&quot;:  &quot;&#39;API error in {microflow} at &#39; + toString([%CurrentDateTime%]) + &#39; - &#39; + $latestError/Message&quot;,<br>    &quot;verbose&quot;:  &quot;&#39;[ERR] {module}.{microflow} - &#39; + $latestError/ErrorType + &#39; | &#39; + $latestError/Message&quot;,<br>    &quot;compact&quot;:  &quot;&#39;{microflow}: &#39; + $latestError/Message&quot;<br>  },<br>  &quot;defaultLogTemplate&quot;: &quot;verbose&quot;,<br>  &quot;moduleLogTemplates&quot;: {<br>    &quot;Integrations&quot;: &quot;apiflow&quot;<br>  }<br>}</pre><p>{microflow} and {module} get auto-substituted with the real names at patch time.</p><p>Different module? Different format. No more “why does this log look completely different from that one” in code review.</p><h3>Why does it skip some microflows?</h3><p>Good question. Here’s the honest answer.</p><p>MDL validates the replacement before writing. If validation fails for a microflow — unusual activity config, edge case, anything — the tool skips it rather than attempting a partial write.</p><p>A partial write to an .mpr is how projects get corrupted.</p><p>So if you see a SKIPPED in your output, that’s not a bug. That’s the tool saying <em>“I’m not confident enough to touch this one — you handle it manually.”</em></p><p>Every skip is logged with the reason. Nothing disappears silently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/0*jvNYiU9YRjQ-BEf6.png" /></figure><p><em>We don’t ship that energy here.</em></p><h3>Safe to re-run. Always.</h3><p>Run it twice. Run it ten times. It doesn’t care.</p><p>The second run looks at everything, finds nothing on default Rollback, and exits cleanly. Anything you’ve hand-tuned since the last run is detected as already-handled and left alone.</p><p>Your manual work is never overwritten. Promise.</p><h3>Install it</h3><pre>npm install -g @vishnuprasath28/mx-error-handler</pre><p><strong>You need:</strong></p><ul><li>Node.js 18+</li><li>mxcli installed and pointing at your project</li></ul><p>Tested on Mendix 9.24 and 10.x. Hit an issue on a different version? <a href="https://github.com/vishnuprasath28/mx-error-handler/issues">Open a bug report</a> and I’ll look at it.</p><h3>The golden rule ⚠️</h3><p><strong>Close Studio Pro before running patch.</strong></p><p>mxcli and Studio Pro cannot write to the same .mpr at the same time. One of them will win. It won&#39;t be you.</p><h3>Links</h3><ul><li>📦 <a href="https://www.npmjs.com/package/@vishnuprasath28/mx-error-handler">npm package</a></li><li>📖 <a href="https://github.com/vishnuprasath28/mx-error-handler#readme">README &amp; docs</a></li><li>🐛 <a href="https://github.com/vishnuprasath28/mx-error-handler/issues">Issues</a></li></ul><p><em>Built this because I had a deadline and 80 microflows and very little patience. Hope it saves you a few hours — or at least a few grey hairs.</em></p><p><em>— Vishnu Prasath</em></p><p><em>If this was useful, leave a clap. If it broke your project… also leave a clap, but also please open an issue. 🙏</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f2daee76a6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/dear-rollback-its-over-signed-mx-error-handler-5f2daee76a6d">Dear Rollback, It’s Over. Signed, mx-error-handler</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ghosting? The Dev Struggle]]></title>
            <link>https://medium.com/mendix/ghosting-the-dev-struggle-66112198ecd1?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/66112198ecd1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[extension]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[code-quality]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 10:40:59 GMT</pubDate>
            <atom:updated>2026-08-06T21:25:19.558Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_OiC32XzRm6gkF0x5OtMGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBsIBsO6gd3_PLgnAt9J3w.png" /><figcaption>Dev struggles everywhere!!</figcaption></figure><p><em>She left. The dead code didn’t. Your unused pages, microflows, nanoflows, attributes and entities are still in your app — rent free — doing absolutely nothing. You (Ahemm) Your app deserves better. Unlike her, they don’t even have the decency to ghost you back. Time to clean house. We built the broom. 🧹</em></p><h3>What it does</h3><p>Dead Code Detector is a Studio Pro 11 extension that scans your Mendix project and finds elements that are defined but never used. It detects unused pages, microflows, nanoflows, entities, and attributes across all your user modules.</p><p>You click Scan project and get back:</p><ul><li>A health score from 0–100 showing what percentage of your project is actively used</li><li>A categorised list of every unused element with its module name</li><li>Results filtered to your modules only — system modules, Atlas, and all marketplace modules are automatically excluded</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPsROiF8icBlfZBjr1AN4Q.png" /><figcaption>Dead Code Detector — HomePage</figcaption></figure><h3>How detection works</h3><p>The logic is simple: collect everything → collect all usages → subtract. What is left is dead.</p><h4><strong>Step 1 — Collect all elements</strong></h4><p>Using pagesApi.getUnitsInfo(), microflowsApi.getUnitsInfo(), and domainModelsApi.getUnitsInfo() to build a complete inventory of pages, microflows, entities, and attributes across scannable modules.</p><h4><strong>Step 2 — Collect all usages</strong></h4><p>Walk every page’s widget tree, every microflow’s action list, and every snippet to find references. All references are stored in a shared RefCollectionContext holding five Sets:</p><p>typescript</p><pre>interface RefCollectionContext {<br>    usedPages: Set&lt;string&gt;;<br>    usedMicroflows: Set&lt;string&gt;;<br>    usedNanoflows: Set&lt;string&gt;;<br>    usedEntities: Set&lt;string&gt;;<br>    usedAttributes: Set&lt;string&gt;;<br>}</pre><h4><strong>Step 3 — Subtract</strong></h4><p>Anything in the “all” map that is not in the “used” Set is dead code.</p><h3>The Main Fall that I faced 🥲</h3><p><strong>The problem</strong></p><p>Pages set as home pages in the Mendix navigation profile always appeared as dead code. Home_Web had zero callers in any page widget tree or microflow action — it is only referenced from the navigation configuration, which lives outside the page and microflow model.</p><p><strong>What we tried</strong></p><p>ApproachResultmodel.resolve(&quot;Pages$NavigationDocument&quot;)Unknown type errormodel.resolve(&quot;Menus$MenuDocument&quot;)Unknown type errorReading .mxunit files via filesApiBinary format — not readableParsing the generated JS bundleHome pages are server-side, not in the bundleReading the .mpr SQLite databaseNo API access to the project file</p><p>Every avenue was blocked. The navigation document type is simply not exposed by the current Extensions API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*FH7gokpVIf9iWrSx7cC7Gg.png" /><figcaption>Navigation Override — Add pages, microflow, nanoflow used in navigation menu</figcaption></figure><h3>Known limitations</h3><p><strong>Navigation-only pages</strong> — pages referenced only from the navigation menu cannot be reliably detected as used. The name-pattern safelist covers common cases but not custom naming conventions.</p><p><strong>Scheduled event microflows</strong> — a microflow that only runs on a schedule has no callers in the model and will incorrectly appear as dead code.</p><p><strong>Java action callers</strong> — microflows called exclusively from custom Java actions have no model-level reference and will appear dead.</p><p>If you are working on a Mendix project that has grown over time, the health score alone is a useful single number for understanding how much cleanup work needs doing.</p><p><strong><em>Link </em></strong><em>🔗:</em><strong><em> </em></strong><a href="https://marketplace.mendix.com/link/component/259480"><strong><em>Mendix Marketplace — Dead Code Detector</em></strong></a></p><p><em>Built with TypeScript, React 18, and the Mendix Extensions API on Mendix Studio Pro 11.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66112198ecd1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/ghosting-the-dev-struggle-66112198ecd1">Ghosting? The Dev Struggle</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Got Relationship Issues? Here’s How Mendix Developers Fix Theirs]]></title>
            <link>https://medium.com/mendix/got-relationship-issues-heres-how-mendix-developers-fix-theirs-3fdbafdc944f?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fdbafdc944f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 11:00:03 GMT</pubDate>
            <atom:updated>2026-07-29T12:25:00.613Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VZ3czvoDRPjhfAkkFudBKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QeRIzgwZYR2-EYG7RWaoHA.png" /></figure><h3>I got this wrong on my first project. Here’s what I wish someone had told me earlier.</h3><p>You’re designing a new domain model in Mendix Studio Pro. You have two entities. You need to connect them.</p><p>Do you just draw a line? Or do you create a third table in between?</p><p>If you’ve ever paused here and felt unsure — this post is for you.</p><h3>First, let’s agree on what we’re talking about</h3><p>In Mendix, when two entities are related, you model that in the domain model as an association.</p><p>But there are two ways to do it:</p><p><strong>🔗 Direct association</strong> — you draw a line between two entities. Mendix adds a foreign key column behind the scenes. Done.</p><p><strong>🔀 Association table</strong> — you create a third, intermediary table that sits between the two and holds references to both.</p><p>Both are valid. The question is knowing <em>when</em> to use which.</p><h3>The direct association — your default choice</h3><p>Think of it like this: an Order has many OrderLines. One order, multiple lines. Each line belongs to exactly one order.</p><p>That’s a classic One-to-Many. You draw a line, set the multiplicity, and Mendix handles the rest — a foreign key gets added to the OrderLine table automatically.</p><figure><img alt="Association image between order and ordertypes" src="https://cdn-images-1.medium.com/max/615/1*HA9kT2GszZKcbhnZ9VZ6sw.png" /><figcaption>Association image between order and ordertypes</figcaption></figure><p>Retrieval is simple too. Your XPath looks like:</p><pre>[MyModule.Order_OrderLine/MyModule.Order = $CurrentOrder]</pre><p>Clean. Fast. Easy to read.</p><blockquote><em>✅ </em><strong><em>Use a direct association when:</em></strong><em> the relationship is 1–1 or 1–Many, and you don’t need to store any extra info on the link itself.</em></blockquote><h3>The association table — when things get richer</h3><p>Now imagine a university app. A Student can enroll in many Courses. And a course can have many students.</p><p>That’s Many-to-Many. A direct association can’t model that cleanly.</p><p>But here’s the thing — there’s more. When a student enrolls, you want to record:</p><ul><li>📅 Enrollment date</li><li>📊 Grade</li><li>🔄 Status (Active / Completed / Dropped)</li></ul><p>Where does that data live? Not on Student. Not on Course. It lives <em>on the relationship itself</em>. That’s your sign — you need an association table.</p><figure><img alt="Associatiom image between student and course (many to many)" src="https://cdn-images-1.medium.com/max/630/1*X0rl8426iqS3BT-8K6PqRw.png" /><figcaption>Associatiom image between student and course (many to many)</figcaption></figure><blockquote><em>✅ </em><strong><em>Use an association table when:</em></strong><em> the relationship is Many-to-Many, this will help in maintaining a seperate table for queries.</em></blockquote><h3>How it reflects in database?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*sid_CfUiG9YEBgIr0EuXgQ.png" /><figcaption>Direct association in database</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*4jP87z9mDfrD4K1Vz21lfA.png" /><figcaption>Association table in database</figcaption></figure><h3>The mistakes I see most often</h3><p><strong>1. Using an association table when you don’t need one.</strong> More entities = more complexity. If it’s genuinely 1-Many, keep it simple.</p><p><strong>2. Forgetting to delete intermediary records.</strong> Deleting a Student won’t auto-delete their Enrollment records unless you handle it in a before-delete microflow or changing the option to delete when the parent gets deleted. Orphaned data will haunt you.</p><blockquote><em>💡 </em><strong><em>Pro tip:</em></strong><em> When in doubt, model your entities on paper first. Ask yourself — </em>does this link have a life of its own?<em> If yes, it deserves its own entity.</em></blockquote><h3>The one question that settles it</h3><blockquote>“Does the relationship itself have something to say?”</blockquote><p>If the answer is yes — it has dates, statuses, quantities, or any data of its own — create an association table.</p><p>If the answer is no — it’s just a connection — use a direct association.</p><p>That’s it.</p><p>Once that clicks, your domain models will be cleaner, your XPaths simpler, and your future-self will thank you.</p><blockquote><strong>Note:</strong> <em>Direct Association was introduced only for the version 10.21 and above.</em></blockquote><p><em>Thanks for reading! If this helped, drop a clap — it tells me to write more of these. 👏</em></p><p><em>Follow me for more Mendix tips and low-code architecture posts.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fdbafdc944f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/got-relationship-issues-heres-how-mendix-developers-fix-theirs-3fdbafdc944f">Got Relationship Issues? Here’s How Mendix Developers Fix Theirs</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Sneaky Mendix Trick to Dynamically Trigger Microflows]]></title>
            <link>https://medium.com/mendix/a-sneaky-mendix-trick-to-dynamically-trigger-microflows-6fec6667a7cf?source=rss-13c8b5bcfec7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fec6667a7cf</guid>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[app-performance]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Vishnu Prasath T A]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 07:54:17 GMT</pubDate>
            <atom:updated>2026-05-07T13:30:57.735Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A Sneaky Mendix Trick to Dynamically Trigger Microflows (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*fJ2C5nn_ALz5C1te_2CiPQ.png" /><figcaption>A Sneaky Mendix Trick to Dynamically Trigger Microflows</figcaption></figure><h4>Using conditional visibility to Optimize Page loading</h4><h4>This article explains a clever Mendix technique that lets you run microflows automatically using Data View visibility. No buttons, no JavaScript — just a clean UI pattern that gives you dynamic control over when your logic executes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJD93M8ESK3rMEs9Lkr1eQ.png" /></figure><h3><strong>What Triggered the Need for This Solution?</strong></h3><p>In my application’s home page, I had to show a large amount of summarized information. Each object had its own set of related records, so every section of the page required separate microflows to fetch data. All these <strong>Data Views</strong> and <strong>Data Grids</strong> were inside <strong>Group Boxes</strong>, and because every data source was a microflow, the home page ended up executing <em>all</em> microflows at once during page load. This created heavy performance issues and unnecessary data processing, even when the user hadn’t opened any Group Box yet. I needed a way to trigger these microflows <strong>only when the Group Box was opened</strong>, instead of loading everything upfront.</p><h3><strong>Experiments: What Worked and What Didn’t:</strong></h3><p>I explored three different approaches to achieve the same functionality, each with its own time complexity, performance impact, and trade-offs.</p><p><strong>NOTE:</strong> Aim is to dynamically trigger the microflow of the dataview that is inside the groupbox ( it has the attribute {description} ). Images have been attached for your understanding.</p><h4>Approach 1: Using JavaScript to Toggle the Data View</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*gWALOlSuveZsvJy_m5xjwg.png" /><figcaption>Using javascript snippet to toggle the boolean.</figcaption></figure><p><strong>Procedure<em>:</em></strong></p><ul><li>Added a custom class to the Data View that needed controlled loading.</li><li>Wrote a JS snippet to detect when a Group Box was clicked or expanded.</li><li>JS located the nearest Data View with that class and toggled its behavior accordingly.</li><li>To map the user’s click to the actual Mendix object, I created a helper entity with a manually generated unique code.</li><li>The helper entity acted as a bridge to identify the correct object</li></ul><p><strong>Issues<em>:</em></strong></p><ul><li><strong>JavaScript cannot access Mendix objects or GUIDs</strong>, so identifying the correct object required a workaround.</li><li>The helper entity and unique-code mapping <strong>added extra processing for every object in the list</strong>.</li><li>Despite reducing some load, this approach <strong>still caused noticeable performance overhead</strong> and became harder to maintain.</li></ul><h4><strong>Approach 2: Using a Nested Data View Inside a List View (List-to-Widget Trick)</strong></h4><figure><img alt="Using list to widget to toggle boolean" src="https://cdn-images-1.medium.com/max/977/1*J_sq-cWKx7P24pUN5UVZ2A.png" /><figcaption>Using list to widget to toggle boolean</figcaption></figure><p><strong>Procedure<em>:</em></strong></p><ul><li>I placed a Data View inside the List View using the <strong>List-to-Widget</strong> option.</li><li>Inside that Data View, I added another Data View whose data source was a microflow responsible for <strong>toggling the boolean attribute</strong>.</li><li>This removed the need for the JavaScript-based trigger from Approach 1.</li><li>Because each list item had its own embedded Data View, I could easily identify the <strong>exact object</strong> the user interacted with and update its boolean attribute correctly.</li><li>This improved performance compared to the previous approach since no extra mappings or helper logic were required.</li></ul><p><strong>Issue<em>:</em></strong></p><ul><li>The List-to-Widget setup works <strong>only when the List View is non-editable</strong>, which restricts how the UI could behave.</li><li>The structure became slightly <strong>nested and harder to maintain</strong>, since it involved stacking Data Views inside each other.</li><li>While more efficient than Approach 1, it still added <strong>extra UI rendering layers</strong> that weren’t ideal for long-term scaling.</li></ul><h4>Approach 3: Switching to Data Grid 2 for Built-In On-Click Handling</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*ExUTygUaf43egu78xt13WQ.png" /><figcaption>Using Data Grid 2 instead of List View</figcaption></figure><p><strong>Procedure<em>:</em></strong></p><ul><li>I replaced the List View with <strong>Data Grid 2</strong>, which immediately made it easier to identify the <strong>exact object</strong> the user interacted with.</li><li>Unlike the previous approach, this change <strong>did not affect the editability</strong> of other Data Views or Data Grids on the page.</li><li>Data Grid 2 comes with a <strong>built-in on-click event</strong>, which allowed me to toggle the boolean attribute directly without extra nesting or helper logic.</li><li>This simplified the overall structure and made the trigger action more direct and controlled.</li></ul><h3>The Final Verdict</h3><p>After trying three different approaches, each with its own strengths and limitations, I realised that every solution either added extra complexity, restricted UI flexibility, or carried unnecessary performance overhead. The JavaScript method worked but lacked object awareness, the List-to-Widget setup helped but limited editability, and Data Grid 2 simplified on-click handling but reduced layout freedom.</p><p>These experiments ultimately guided me toward a cleaner, more efficient, and fully Mendix-native solution — using <strong>Data View visibility</strong> <strong>to trigger microflows only when needed</strong>. It kept the UI simple, improved performance, and delivered exactly the control I wanted without relying on unnecessary workarounds.</p><h4>Read more</h4><ul><li><a href="https://docs.mendix.com/refguide/common-widget-properties/#visibility-properties">Properties Common in the Page Editor</a></li><li><a href="https://docs.mendix.com/refguide/on-click-event/#triggering-actions">On Click Event and Events Section</a></li></ul><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fec6667a7cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/a-sneaky-mendix-trick-to-dynamically-trigger-microflows-6fec6667a7cf">A Sneaky Mendix Trick to Dynamically Trigger Microflows</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>