skills.rest
engalar
engalarCOMMUNITY
Explore all skills by this author →
GitHub

page-data-design

Guides Mendix page data architecture by selecting datasource types and container layouts.

1|Updated Jun 5, 2026
Search Tags:#architecture#dataview#datasource#datagrid#mendix#npe
One-click install
npx skills add https://github.com/engalar/mxcli-taskdemo --skill page-data-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: page-data-design
Source: https://github.com/engalar/mxcli-taskdemo/tree/main/TaskDemo/.claude/skills/data-containers
Command: npx skills add https://github.com/engalar/mxcli-taskdemo --skill page-data-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves common architectural challenges in Mendix page design, specifically regarding how data is fetched, displayed, and managed across different container types to ensure optimal performance and maintainability.

Core Features & Use Cases

  • Datasource Selection: Provides a decision framework for choosing between database, microflow, nanoflow, or parameter-based data sources.
  • Container Optimization: Offers best practices for nesting DataViews, DataGrids, and Galleries to avoid N+1 query issues and unnecessary server round-trips.
  • Use Case: Use this skill when you need to determine whether to use a database source for a persistent entity list or a microflow for a non-persistent entity (NPE) to ensure your page functions correctly at runtime.

Quick Start

Use the page-data-design skill to evaluate the datasource strategy for a new order management page containing a master-detail layout.

Frequently Asked Questions about page-data-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right datasource for a Mendix DataView or DataGrid?▼

Choosing a Mendix datasource depends on entity type: use database sources for persistent entities and microflow or nanoflow sources for non-persistent entities (NPE) to ensure runtime functionality and performance.

What's the best way to design a Mendix master-detail layout without causing N+1 query issues?▼

Designing master-detail Mendix layouts requires optimizing nested DataViews and DataGrids to minimize server round-trips, preventing N+1 query issues by validating datasource compatibility and selecting appropriate containers.

When should I use a microflow datasource instead of a database datasource in Mendix?▼

Use a microflow datasource in Mendix when displaying non-persistent entities (NPE) or when complex logic is needed before rendering, whereas database sources suit direct persistent entity lists for better performance.

Why does my Mendix page with nested DataViews experience slow load times?▼

Slow Mendix page load times often result from poorly nested DataViews and DataGrids causing unnecessary server round-trips, which can be fixed by optimizing container data architecture and datasource selection.

Can I use a nanoflow as a datasource for a Mendix overview grid?▼

Yes, nanoflows can serve as datasources for Mendix overview grids, particularly for non-persistent entities or offline scenarios, ensuring adherence to performance standards by minimizing server round-trips.

Related Skills

Explore More Software Engineering Skills→
engalarengalar
1

MDL Entity Syntax Reference

Reference MDL syntax for Mendix domain model entity definitions.

Community
Basic
engalarengalar
1

write-microflows

Generates syntactically-correct MPython-like MDL code for microflows and orchestrates complex tasks with acyclic graphs of

Community
Advanced
engalarengalar
1

create-page

Generate Mendix page definitions and UI widget structures using MDL statements.

Community
Intermediate
engalarengalar
1

master-detail-pages

Create synchronized master-detail UI patterns in Mendix using MDL scripts.

Community
Intermediate