Hi Sudarsanam,
The <...> caption is what the Combo Box (Database mode) shows when the selected option can no longer be found in its options list. The widget keeps track of the selected option object, not just the value. When the options list is reloaded with different objects, it can’t find the previous one and shows <...>.
In your case, Refresh in client causes the selectable-objects microflow to run again. If that microflow creates the option objects (for example non-persistable objects), each run returns new objects with new IDs, so the combo box loses its link to the selected option.
How to fix it
If the value you store represents an object anyway, consider using an association instead of a string attribute. The combo box then works directly with the object and doesn’t need to match values.
Kindly accept the answer if it resolves your query.
Hi Sudarsanam,
Since the combo box intermittently displays <...> after a refresh, I would first verify that the selected value is still valid and can be resolved against the options returned by the datasource.
1. Verify the selected value and datasource results
If the selected value is missing from the returned options, correct the datasource or the logic that sets the selection.
2. Check the combo box binding
If the combo box stores a string or integer value, verify that the configured selectable values and target attribute are compatible.
If it uses an association, verify that the selected object belongs to the expected entity and that the association is configured correctly.
3. Check the caption configuration
Verify that the caption attribute or expression is populated for the selected option. If the caption depends on another associated object, check that the required data is available and accessible.
4. Avoid unnecessary refreshes
Make sure the update microflow completes before refreshing the relevant object in the client. If the value is set through a nanoflow, ensure that the update and refresh happen in the correct order.
As a diagnostic test, temporarily remove the additional refresh logic and see whether the issue still occurs. Do not add more refreshes until you identify which object needs refreshing.
5. Test with a simplified configuration
Temporarily use a database datasource with a small, predictable set of options. If the issue disappears, compare that configuration with the original microflow datasource to identify differences in the selected value, returned options, or captions.
Also check the browser console for errors when the combo box displays <...>.
Reference: Mendix Combo Box Documentation
My recommendation: Start by verifying that the selected value set by your microflow matches an option returned by the datasource. This is the first thing I would investigate before changing the refresh logic.
Hope this helps! If you find this answer helpful, please mark it as the accepted answer.
Had the same. Troubleshooting from Gowtham is useful. Also the problem can be language settings in some cases.
Hi Sudarsanam,
Another thing worth checking is whether the value shown in the Combo Box is translated or derived from an enumeration caption.
I've seen <...> appear when:
The selected value exists in the database, but the corresponding option is filtered out by the selectable-objects microflow.
Security rules prevent the current user from retrieving the selected object.
The caption attribute is empty or language-dependent, and the value is not available in the current language.
As a quick test, temporarily:
Remove any filtering from the selectable-objects microflow.
Log the selected object's ID/value before and after the refresh.
Verify that the selected object is included in the returned list after the refresh.
Check with another language and user role to rule out localization or security-related issues.
If the issue occurs only after a Refresh in Client, I would especially verify that the selected object is still returned by the options microflow and has not been filtered out due to changed context or access rules.
In most cases where I've encountered <...>, the root cause was that the selected object was no longer present in the list returned to the Combo Box after the refresh.
Hope this helps.