executeMicroflowAsUser_1 object being passed changes when passed

[RCatersels]

See also forum post https://forum.mendixcloud.com/link/questions/96621
To me it seems that the object being passed reverts to the state at the beginning of the microflow not the state the object has at the moment when being passed.
Rene created a test project (see the forum post).
It looks like the problems started with Mx7.23.7.
Regards,
Ronald

[reinouts]

Hi Ronald,

Thanks for raising this issue. I'm attaching the test project so that we don't lose it.

BckGrndDateAndMFAsUser1Test.mpk.zip

[reinouts]

@RCatersels I've imported the test module into a 7.23.7 project and tried to reproduce the issue, and failed to. Can you give a clear reproduction scenario?

[reinouts]

Ping @RCatersels - is this still an issue? If I don't get any response, I will close this issue for lack of information.

[RCatersels]

Sorry did not see the message in December. When I create a new test project I can not reproduce it. The dirty state of the object is passed along to the microflow. But in our model we do sometimes have this problem. When I debug the microflow I suddenly have the state of the object as it was last saved in the database and all the changes prior to calling this action are not there anymore. Most of the time I can workaround it but I fail to grasp why this is happening.
Regards,
Ronald

[RCatersels]

I just had a brain wave because indeed the dirty state of the attributes of that object are passed along. But any changes to associations are not. It does not matter if I commit the associated object first before doing the actions. The association is empty after the object is passed along. I would expect that if the object is passed along that also any changes in associations are passed. Or is that assumption wrong? If you want I can give you my quick and dirty test project.
Regards,
Ronald