I notice when grid autoCommit is set to True, adding a new row, then editing this row late on. It logs two transaction - new row and edit row (same rowId). But if autoCommit = false, it logs one transaction. In both cases, aggregateTransactions is set to true.
Is there any way to log one transaction in the first case?
Thanks,
Michael
Hello Michael,
When “autoCommit” option of the grid is set to “true” the transactions are committed automatically as rows or cells are being edited.
Can you specify what version and build of our controls you use and what is the type of the Data Source used for this grid?
I'm using 12.2.20122.2056. And my data source is simply a object array.
I attached my sample. It seems that aggregateTransactions setting only works when autoCommit is false. If it is by design, is there way to get aggregated transactions?
Hi Michael,
The truth of the matter is that the aggregateTransactions option works for the "pending" transactions log.This transaction log plays a role in the updating functionality only if autoCommit is set to false.Thus, a more complete description of the option would state that it assists in the aggregation of pending transactions.(we currently take it as a given that it's reasonable that only pending transactions to be subjects of aggregation).A more detailed explanation would be that "pending" transactions are both reflected in the grid as pending and they are present until something calls or triggers the commit() API method.The transactions that are sent to the server are very similar in purpose, but they live until the saveChanges() method is called explicitly (and this method is not needed for a scenario where the igGrid is bound to client-side data) and they aren't really reflected in the igGrid's UI.Thus we had decided that the "pending" transactions are the ones that are subjects to aggregation.Hope this helps!Cheers!