Hi Community,
I would like to propose a feature that would greatly simplify the process of working with large domain models in Mendix, especially when there are many tables with numerous attributes.
The idea is to enable the creation and export of the entire database (domain model) through a JSON format. This feature would make it much easier to manage large domain models, allowing for quick import and export across different Mendix projects. It would also facilitate copying and pasting entities between applications, regardless of the Mendix Studio Pro version being used.
Currently, I've faced challenges when trying to recreate an application or transfer domain models between different apps. If the versions of Mendix Studio Pro do not match, copying and pasting entities is not allowed, leading to a time-consuming manual process of rewriting the entire domain model.
Having the option to create, export, and import the domain model in JSON would not only save time but also improve efficiency when working on large-scale projects or when transferring models between apps.
Thanks!
Hi, I wonder if there is a way to export/import the domain model of a module. I am interested in developing a domain model importer from another technology to Mendix (and visceversa). For example, to go from a PlantUML class model to a domain model in Mendix. But in order to transform the PlantUML class model to Mendix, I have to know the import format of the domain model in Mendix. For example, JSON (but I see that it is not possible at the moment).
Is there any way to export/import domain models from Mendix to a readable format like XML, JSON or any other?
David,
Your idea of enabling the creation and export of the entire domain model in JSON format in Mendix has some clear pros and cons such as:
Pros:
Cross-Version Compatibility - JSON format would allow seamless export and import of domain models between different Mendix Studio Pro versions. It would solve the current issue of being unable to copy and paste entities across different versions, greatly improving flexibility.
Simplifies Collaboration - Teams working across different applications could share models much more easily. This could be especially helpful in multi-developer projects, improving workflow by allowing better sharing of domain models across different team members and projects.
Cons:
Potential for Human Error - Manually editing JSON files could introduce errors into the domain model. If users tweak the JSON file directly, it might lead to issues or corrupted domain models when re-importing them into Mendix Studio Pro.
Security and Data Integrity Concerns - Exporting domain models as JSON might present data security risks if not properly managed. Ensuring the integrity of exported/imported models and safeguarding them during transfers would be crucial, especially in enterprise environments where sensitive data could be involved.
Overall, your suggestion would greatly improve workflow efficiency, especially when dealing with large domain models or multiple apps. However, careful consideration would need to be given to maintaining compatibility with Mendix’s built-in features and ensuring data integrity during transfers. Thank you for sharing.
Shelly D. Kirk-Selvester