While debugging a Mendix application, I recently needed to determine where an entity was being deleted. My first instinct was to use Find Usage in actions, which works well for locating object operations in microflows and event handlers.
However, the actual deletion was triggered through a built-in Delete button on a page, and it took additional manual effort to identify the source.
Find Usage provides visibility into activities such as:
Create Object
Change Object
Commit Object
Delete Object
Event handlers
But it does not provide a consolidated view of CRUD operations performed through built-in UI actions, such as:
New button
Delete button
Edit button
Data Grid/Data Grid 2 built-in actions
As a result, developers may need to manually inspect pages and widgets to understand where an entity can be created, modified, or deleted.
Extend Find Usage in actions or Find Advanced so that it also reports built-in UI actions that operate on an entity.
For example, searching for an entity could return results like:
|
|---|
Faster root-cause analysis during debugging
Reduced time spent manually inspecting pages
Better impact analysis before making changes
Complete visibility of all entity entry points
Improved maintainability for large applications
A common troubleshooting question is:
"Where can this entity be deleted?"
Today, Find Usage in actions can help identify delete operations implemented in microflows, but developers may still miss deletions triggered directly through page buttons or grid actions. Including these UI-driven actions in search results would provide a more complete picture and significantly improve developer productivity.
Would other Mendix developers find this useful? I'd be interested to hear whether you've faced similar challenges while tracing entity lifecycle operations.