Hi,
I have a v2014.2 igGrid which uses a JSON datasource and pages locally. I have updating enabled on the grid. When I add a new row and click the "Done" button on the add new row template, the new row appears in the grid (text in italics). However, the total row count displayed on the grid does not get updated, and the row also disappears from the grid if I page forward and then back again. The new row does not appear on any of the pages. When I post the form and process the grid transactions, the addedrow is in the transactions list,
Why does the row not stay in the grid or clientside JSON datasource while I am paging and the total row count display not get updated?
There also appears to be an error being thrown in the infragistics.lob.js script: "Uncaught Error: Grid has pending transactions which may affect rendering of data. To prevent exception, application may enable "autoCommit" option of igGrid, or it should process "dataDirty" event of igGridUpdating and return false. While processing that event, application also may do "commit()" data in igGrid."
Any ideas? Thanks.
I see using the AutoCommit = True option ensures the added row appears in the grid when paging.
The total row count (1 to x of y) display is unchanged however.
Another question I have is why editing (row editing or adding a new row) is only enabled when ShowHeader = True? I have a scenario where I have only one column and do not want to show a header but do want to be able to edit an existing row or add a new row. The only thing I can do when ShowHeader = False is delete a row?
Why is this the case?
Hi Tsanna
I am specifying my grid configuration in the MVC model, not in Javascript.
I have attached a sample project which shows the issue. Run the code to load the index page, and then add a new row to the grid. You will see that the row is added/committed, but the total item count stays the same.
Regards
David
I have got this working by not using the inbuilt "Add New Row" functionality, but by calling the igGridUpdating addRow method via my own button click.
I would just add that the documentation seems light given an API that seems over-complex. Trial and error should not be the way developers should be using your controls as it is time consuming and leads to an inclination to look elsewhere.
Hello duster.
Thank you for your feedback and I'm glad you were able to resolve your issue.
If you have any concerns or disappointments related to using trial version of our product, respectively trial support service level, I would suggest you to consider purchasing our product. Here is an explanation of the support benefits that you'll gain after purchasing our product depending on the support level: http://ko.infragistics.com/support/support-policies For more information about the purchasing process, you may refer to the following section on our website: http://ko.infragistics.com/about-us/contact-us If I can provide further assistance, please let me know.
Regards,
Tsanna
I have purchased multiple Infragistics products in the past, namely:
NetAdvantage for .Net 2007 Vol 3 Corporate
NetAdvantage for .Net 2008 Vol 1 Corporate
NetAdvantage Ultimate 2011 Vol 2
NetAdvantage Ultimate 2012 Vol 1
NetAdvantage Ultimate 2012 Vol 2
Infragistics Ultimate 2013 Vol 2
Infragistics Ultimate 2014 Vol 1
and lastly
Infragistics Ultimate 2014 Vol 2
So I have plenty of experience with the product and the support offered by Infragistics. My original point still stands and in fact should be further underlined for you given my extensive experience firstly in 30 years of software development and secondly in over 8 years of working with various Infragistics offerings.
Hello duster,
Thank you for sharing your opinion with Infragistics community.
Regards,Tsanna
My intention was not to share my opinion with the forum, but in the hope that Infragistics takes note of my point re documentation and complexity of API as you have a good set of tools which have served me well in the past, I just feel the quality of the product is let down by the depth of the documentation given the API. Every API method/event/option, etc is listed, but the breadth and depth provided per item could do with a lot more detail and usage examples.