Saving one row per transaction
With primary and secondary collections, you can instruct the application to save each modified row (IDO item) in a separate transaction. When the user executes the save operation on the collection, the application loops through modified rows, executing a "Save Current" operation for each row. If the save succeeds, the application moves to the next row. If it fails, the application stops and presents an error message. The previous rows remain committed.
In the default behavior, all modified rows are sent to be processed within a single transaction, which is rolled back if there is a failure.
Note: If your form design requires that all modified rows be committed as a
unit, with processing on the unit before and/or after a save operation, saving rows in
separate transactions might not be appropriate: In a case like that, if an error occurs
on a row, some rows might be committed and others not committed.