What you are seeing is expected behavior.
A microflow data source is executed when the widget is loaded or when its context is refreshed. It is not designed to run again every time the user simply opens the dropdown. Mendix also uses client-side caching for loaded objects, so reopening the Combo Box usually does not trigger a new server call by itself.
So the direct answer is: no, a normal click on the Combo Box will not automatically re-run the microflow every time. If you need fresh data each time, you need to explicitly refresh the context that drives the widget. When an object is refreshed in the client, relevant data sources are reloaded.
Best-practice options:
If you are using the Marketplace Combo Box widget, it does have events such as On enter action and options like Lazy loading, but those are still not the same as “run the data source microflow on every click.” They can help you trigger your own refresh logic before the user selects a value.
So in practice, the clean solution is:
If this resolves your issue, you can mark it as accepted.
Hi,
This is expected behavior when using a microflow as the data source for a Combo Box in Mendix.
When a Combo Box is configured with a microflow data source, Mendix executes that microflow only when the widget is initialized (i.e., during page load). After that, the results are cached on the client side, and clicking the Combo Box again does not re-trigger the microflow.
So by design:
There is no direct “on click reload” option for a Combo Box, but you can achieve this using one of the following approaches:
Then:
This ensures the Combo Box always reflects updated data.
Since Combo Box does not have an “on open” event, you can:
This forces Mendix to reload the data source.
If you strictly need reload on every dropdown open, the standard Combo Box will not support this.
In that case:
onFocus / onClickThis gives full control over when the data is loaded.
Mendix is designed to avoid unnecessary server calls, so it caches data intentionally. Continuously calling a microflow on every click can impact performance.
Recommended approach:
Thank you ,