Hello,
I have a virtualized grid with autoCommit & aggregateTrans. set to true. There are few properties which are not binded to the grid as columns. There is a difference in the row object which has all the cell values modified during a row update. Am sure this did not happen in 2012.1 release, but is now seen in the 2012.2 and the recent SR. Here is a scenario.
I have a grid with two rows already present. I add a new row and commit the changes (by hitting enter). I then update the same row by changing some cell value and then commit. When i see the 'allTransactions' object, there are 'newrow' and 'row' types of elements. In the 'row' element type, i see the value of the hidden column being set to null in addition to the modified properties. This does not happen when the grid has any rows already present. This behaviour starts from the third row.
We need this behaviour to be consistent with the old one since we copy all the properties of the 'row' element type to a new object to get the final changes to the row. The additional hidden columns with NULL values will result in an error in our application.
Attaching demo source code for your reference.
Thanks,
Wajid.
Hi Wajid,
Thank you for posting on our forums!
Thank you for providing a sample with this. I am seeing the behavior you are describing with it and I will need a little more time to research this issue.
I will have another update on my findings for you tomorrow.
Hello Wajid,
Thank you for your patience.
I have reviewed this scenario and have logged this behavior with our engineers for further investigation. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 140939. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
Please let me know if you need more information.
Hello Wajid,Thank you for your patience.
After reviewing the matter, our engineers have concluded that in order to not transform the transaction based on the local data in this case, the localSchemaTransform option of the grid would need to be disabled (it is enabled by default). Setting this option to false would instruct the igDataSoruce to not try and transform the data in this case.
Attached is a modified version of your sample illustrating this in practice for your reference.
Please do not hesitate to contact me if you have any questions.
Please feel free to contact me if you have any further questions regarding this matter.