How to use Non-Persistent Entities in Tree Table and Save/Cancel Changes Properly?

0
Hi everyone, I’m working with a Tree Table in Mendix that displays a hierarchical structure of four entities, each associated in a one-to-many relationship (like A → B → C → D). I want to: Allow users to add or edit data in the tree view. On Save, commit all data to the database. On Cancel, discard all changes (nothing should be saved). Currently, I’m using non-persistent entities to handle the in-memory data and only commit them to persistent entities on Save. However, I’ve noticed that: The Tree Table does not allow nested levels when using non-persistent entities (it only works for one level). Has anyone found a way to: Display multiple nested levels (A → B → C → D) in a Tree Table using non-persistent entities? Or is there a better approach to achieve the same Save/Cancel behavior with persistent entities (e.g. rollback on cancel)? Any suggestions or best practices would be greatly appreciated!  Thanks in advance!
asked
1 answers
0

Hi Sachin,

 

If you are working in a closed environment which means your application is restricted in a network, then I would do the same thing with persistent entities. You can then explicitly save and/or delete created tables with dedicated microflows. 

 

Ferhat

answered