In Mendix Studio Pro 11.8, Maia is quite capable when it comes to generating and modifying domain model elements. You can use it to create entities, add attributes, and define associations quite efficiently, which makes initial modeling and iterations much faster.

However, when it comes to delete operations, Maia is still limited. Based on current behavior, it does not reliably perform destructive actions such as deleting entities, attributes, or associations. Even if prompted, these operations are usually ignored or not executed fully.

The main reason behind this limitation is safety. Deleting elements in the domain model can easily break references in microflows, pages, or other parts of the application. Because of that, Mendix keeps these actions under developer control rather than allowing Maia to handle them automatically.

So in practice, the recommended approach is to use Maia for creating and updating your model, but handle deletions manually. Before deleting anything, it’s a good idea to use “Find usages” to understand dependencies and avoid runtime issues.

In short, deletion is still a limitation in 11.8, and manual cleanup remains the best and safest approach for now.

If this resolves your issue, you can mark it as accepted.

Hi,

In Mendix Studio Pro 11.8, Maia (Maia for Domain Model / Maia Make) can assist with generating and modifying domain model elements, but it does not reliably support delete operations such as removing entities, attributes, or associations.

Current Behavior in 11.8

From practical usage and current capabilities:

• Maia can create entities, attributes, and associations
• Maia can modify existing structures
• However, delete actions are limited / not supported consistently

In most cases, Maia will:

• Avoid deleting elements automatically
• Or require explicit manual confirmation/cleanup by the developer

Why deletion is limited

Deletion in a domain model is a destructive operation and can have side effects:

• Breaking microflows/nanoflows
• Invalidating pages and widgets
• Causing runtime or consistency issues

Because of this, Maia is intentionally conservative and does not aggressively perform delete actions.

For now, the correct and safe approach is:

• Use Maia for:
  • Creating entities
  • Adding attributes
  • Structuring associations
• Perform deletions manually in Studio Pro:
  • Delete entity/attribute/association directly in the domain model
  • Resolve any dependency warnings shown by Mendix

• Maia in Mendix 11.8 does not fully support delete operations in the domain model
• This is a current limitation by design, mainly for safety
• Developers should handle deletions manually to ensure consistency

This aligns with the current behavior of Maia in Studio Pro 11.x and is the recommended way to work with domain model changes today.