Hello everyone, I'm facing an issue with my application's workflow and would appreciate some guidance. Problem: When a reviewer clicks on a submitted request to view its details, an empty, new request object is being created and saved to the database. This happens even when the reviewer is simply trying to open and view the existing request. The expected behavior is that the click action should only open the existing object's details, not create a new one. Scenario: An applicant submits a request, creating a Request object. The reviewer sees a list of these requests. The reviewer clicks on a specific Request object in the list. An empty Request object is created and committed to the database. The reviewer's page shows a form that is seemingly tied to this new, empty object, not the original one. What I've Checked: I've traced the microflow that is triggered by the "On click" action on the data grid. The microflow does not have a "Create Object" activity for the Request entity. It simply takes the selected Request object as a parameter and opens a page. I suspect this might be related to Mendix's autocommit behavior, but I can't pinpoint where it's happening, especially since I'm not explicitly creating a new object in the microflow. Could this be an issue with the page's data view configuration? Any ideas on what might be causing an empty object to be created when I'm only trying to open an existing one? Thanks in advance for your help!
asked
waad bada
2 answers
0
Apperantly you are triggering a create object (and even commit) in your action flow.
I would suggest you to go to the domain model and right click the entity -> click "Find usages in action" then select only "Create" in the modal page (as follows) and find the Create usages in your project.
Afterwards right click the find result tab and lock it and go over the find results (pages/microflow/nanoflow) that has create for that entity. And for each microflow / nanoflow right click and find usages of that particular microflow which has a create action. At the end you may be able to find out which action triggers that additional entity creations.
answered
Tolga Ozden
0
Dear Tolga,
there are only 2 microflows that creates the entity and none of them are set to commit.