What is the best practice when multiple sub-microflows retrieve data from the same entity?

The best practice when multiple sub-microflows retrieve data from the same entity is to retrieve the data in the main microflow and pass it as an input parameter to each sub-microflow. This approach has several advantages that enhance efficiency and performance within the Mendix application.

By retrieving the necessary data once in the main microflow, you minimize the number of database calls. Each sub-microflow can then operate on the same data without needing to query the database again, which reduces overhead and improves application performance. This method also enhances maintainability; if the way data is retrieved needs to be modified, you only have to update the main microflow rather than each sub-microflow individually.

Additionally, passing parameters allows sub-microflows to execute with the exact context they need without being dependent on their own data retrieval logic. This creates a cleaner and more modular design, which aligns well with best practices in software development and promotes code reuse.

In contrast, retrieving data in each sub-microflow separately can lead to redundancy and an increase in database load. Similarly, retrieving data only when needed may lead to performance bottlenecks, especially if data is accessed repeatedly in various parts of the process. Continuing with the current approach without optimization could hinder scalability