Sub-microflow changes to a list dont reflect back in the original instance of the list.
1
This is a question for my own sanity: When passing a list to a sub microflow, iterating over that list and making changes to that list in the iteration doesn't reflect back in the parent microflow. When continuing with the list in that parent microflow. I believe that this used to be done in lower version of Mendix but can't recall a date or release when this behavior has been changed. Perhaps I'm mistaken and it's always worked like this, but it's very inconvenient that the sub microflow gets it's own instance of the list and doesn't reflect it's changes back to the parent without committing those changes and re-retrieving them. So unless you return the full new list from the sub microflow you don't really get new data. So maybe someone can elaborate on what has been altered? Perhaps it's a Mendix 7.23 issue that has sneaked in? Or am I just being an idiot (as this always has been an obvious option to myself, perhaps can someone confirm it this time).
I don’t have a current example, but I was also under the impression that changes you apply to a list in a submicroflow will reflect in the parent microflow. Did you also try to add/remove items from the list? Or are you only changing the objects in the list?