JSON Structures, Import Mappings & Export Mappings

Create and manage JSON structures, import mappings, and export mappings in Mendix using MDL.

1|Updated Jun 5, 2026

Search Tags:#integration #rest #json #mapping #mendix #mdl

Ready to run

npx skills add https://github.com/engalar/mxcli-taskdemo --skill json-structures-import-mappings-export-mappings

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: JSON Structures, Import Mappings & Export Mappings
Source: https://github.com/engalar/mxcli-taskdemo/tree/main/TaskDemo/.claude/skills/json-structures-and-mappings
Command: npx skills add https://github.com/engalar/mxcli-taskdemo --skill json-structures-import-mappings-export-mappings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of integrating external JSON data into Mendix applications, specifically solving the common pitfalls of domain model structure for import versus export operations.

Core Features & Use Cases

JSON Schema Definition: Quickly define JSON structures from snippets to auto-derive element trees.
Mapping Logic: Implement robust import and export mappings, including nested objects and array handling.
Use Case: When building a REST integration, use this skill to correctly structure your non-persistent entities to mirror JSON payloads, ensuring seamless data serialization and deserialization.

Quick Start

Use the json-structures-and-mappings skill to generate the necessary import mapping and domain model entities for a new REST API response.

Frequently Asked Questions about JSON Structures, Import Mappings & Export Mappings

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

FAQPage Schema

How do I map nested JSON arrays to entities in Mendix?▼

Mendix import mappings handle nested JSON arrays by aligning non-persistent entities to mirror the payload structure, ensuring seamless deserialization of complex REST integration data.

What's the best way to structure domain model entities for REST API JSON consumption?▼

Structuring non-persistent entities to mirror inbound JSON payloads is the best way to consume REST API data, allowing the import mapping to correctly parse nested objects and arrays during serialization.

How do I generate JSON structures from snippets for Mendix integrations?▼

You can paste JSON snippets into the JSON structure definition tool to auto-derive the element tree, which then generates the necessary domain model entities and import mappings for your integration.

Why does my Mendix export mapping fail to serialize complex JSON correctly?▼

Export mapping serialization fails when persistent-to-non-persistent entity transformations are misaligned, requiring domain model structure adjustments to correctly mirror outbound JSON payloads for REST API responses.

Can I handle persistent-to-non-persistent entity transformations for JSON integration in Mendix?▼

Yes, JSON integration mappings support persistent-to-non-persistent entity transformations, ensuring correct domain model alignment for both inbound data consumption and outbound API serialization scenarios.

When do I need non-persistent entities for Mendix REST integrations?▼

Non-persistent entities are needed when building REST integrations to correctly structure your domain model to mirror JSON payloads, ensuring seamless data serialization and deserialization without database persistence.