Hi,

I have a grid in which I'm overriding the primary key generated by grid using generatePrimaryKeyValue event. I'm setting the value to 0, as my business logic will take care of generating the new primary key.

I have aggregate transactions set to true .

If I add two new rows and then delete the second one and finally commit the changes, the second row is getting saved and first one is deleted.

I believe this is happening because the aggregation works on primary key and both my rows had primary key as 0.

Is there any way to get around this ?