Issue on AutoCommitted Objects

Some autocommitted objects still existed on logout for session 'Anonymous_d51a3fd1-34d3-4394-8e2e-b85f44f7a173'. Autocommitted objects are newly created objects which were not yet committed, but are inserted into the database because an associated object was committed. Autocommitted objects should explicitly have been committed, please check your model and apply the necessary changes. The autocommitted objects have been deleted from the database to prevent database corruption.Number of autocommitted objects per type which still existed for this session: - XYZ.Entity: 1 object(s). Please suggest.
2 answers

This means that you should ckeck your model on not committed nested objects. Let's say you have a page with a main object and some nested child objects. When you use the regular save action on this page the main object get's saved but not the child objects. If you do not do this with an onchange action in the form or with a custom save button you get the message above.

Sollution: either use a on change commit microflow in your child objects or use a custom save action where you commit the parent object and do a retrieve and commit on all the child objects of that page.




Most times you can't do anything about this error. The suggestion that this is a modeling error is most time incorrect. See