Hi Remington, you can use Task Queue is one of the best ways to handle this in Mendix, especially with large datasets like 200k+ items. It avoids runtime and memory issues by offloading processing to background threads and reducing memory pressure from long-running loops.
Task Queue is a great fit even for something as simple as adding or updating a Boolean on 200k+ items. It is absolutely appropriate and recommended, even for a simple Boolean update, when you're working at this scale. It will save you from performance and runtime issues.
I hope this one helps you :)
For each checkbox, you need to create a separate Boolean attribute. Additionally, when the checkbox's value changes, you should trigger an on-change event, either by using a microflow or a nanoflow.
Here's a step-by-step breakdown:
Example
Let's say you have a checkbox for "Pay by Credit Card". When its value changes, you'll want to update the object with the corresponding payment method.
Further Exploration
You might want to explore how to reuse common checks across multiple microflows by creating a new rule in Mendix. This could be a valuable technique for maintaining consistent validation logic across your application.
If this helps , accept my answer
5 references
Retail application
April 6, 2021
Get data acording to check box selected
Accepted Answer
January 21, 2023
How to check if 2 numbers match
Accepted Answer
September 4, 2020
Adding Multiple items in an ORder.
November 25, 2021
StudioPro 9.14.1 Native-How to search an Entity Attribute to assign to a different Entity Object Attribute
June 29, 2022