Inconsistent import location when installing Mendix modules offline using .mpk files

Issue

When importing offline copies of Mendix modules (.mpk files) into a Mendix project using the Import module package option in App Explorer, the modules appear in inconsistent locations. Some modules are imported under the Marketplace modules folder, while others are imported outside of this folder as a new module.

For example:

• CommunityCommons_11.5.0.mpk imports outside of the Marketplace modules folder
• MxModelReflection_9.1.0.mpk imports inside the Marketplace modules folder

This inconsistency creates issues when working in environments with firewall/proxy restrictions that block direct Marketplace downloads, and where IT-approved software and audit traceability are required.

Environment

Studio Pro (all versions)

Cause

The import location of .mpk files depends on where the module was originally exported and published to the Mendix Marketplace. Modules that were created and exported from the Marketplace folder, they will be imported into the Marketplace modules folder. In contrast, modules that were not created and exported from the Marketplace folder (or were created as custom modules) will be imported outside this folder, directly into the App Explorer structure.

Studio Pro only forces the module to be a marketplace module when it is added through the Marketplace tab directly, as then all information is available to update the module on import.

This is expected behavior in Mendix Studio Pro.

Solution/Workaround

The module's origin determines the import location behavior and cannot be manually controlled through the import process. 

Additional information

• Mendix documentation:
  • How to Use Marketplace Content
  • Using Marketplace Content