So I just got the latest update and I can no longer make updates. The I try to update my code I get this attached look. I do my updates a bit different so I'd rather just like to know what this is and how to turn it off.
Hello seang,
Thank you for posting in our forums!
Please answer the following questions so I may have a better understanding of this issue:
a.) What is the version and build you are upgrading to? e.g. 13.2.20132.2212
b.) You say you handle updates differently. Could you please provide more details on how you are updating the grid?
c.) When does this popup box appear? During row editing mode, when the grid renders, or some other time?
Looking forward to hearing from you.
a) version 20141.2031
b) not really, I have had many complications dealing with primary keys. Some of your staff is familiar with how I do updates and there are a lot of forum posts about it. In short I have to by pass all the normal events. Like hitting enter after a cell is updated or double clicking to enter update mode. To update cells I use something like this
var text = this.gridIDMap.cellAt( cell.index, cell.rowIndex )
text.innerHTML = ...
c) seems to only happen when I'm editing the primary key column. Maybe its during the call to editCellEnding.
I was hoping you could just tell me what would make that box pop up? Looks like you possibly do not know? Thus I maybe on my own to figure it out here.
Hi seang,
I need a little more time to look into these 2 new issues.
I will have another update for you by Thursday. I am fine with leaving this out in the forums as some other users may find the information useful.
Daniel Dority,
Thank you for your feedback and offering your assistance here. Your post is very informative and thorough.
I was able to fix (3) seemed to be the fact that adding a primary key column as string was not helping. This could be a simple check for error handling I think.
Still can't seem to get (2) resolved.Did some searching with ie debugger and I get this sizzle error. On google searches it points to needing the div name in quotes.http://stackoverflow.com/questions/11849104/jquery-syntax-error-unrecognized-expression-name-basics-genderNot sure if its related or not.
Also when updating more the one column in a selection I get this
"Error: cannot call methods on igEditorFilter prior to initialization; attempted to call method 'remove' " from a function called isEmptyObject in jquery. Stack shows _endEdit to be the last called method.
Once this occurs the grid is no longer responsive to events of any kind.
This is the way I update selections
if ( cells ) //current cells in edit mode{ for ( var c = 0; c < cells.length; c++ ) { INSTANCE.igGridUpdating.setCellValue( cells[c].rowIndex, cells[c].columnKey, ui.value) }}
Is there an issue using setCellValue in editCellEnding ?
Yes, currently you cannot execute setCellValue on editCellEnding. This is a side-effect to another change that enabled column templates to re-execute after updating for the whole row. You can, however, call setCellValue on editCellEnded, or even better use the event argument "value" of editCellEnding to modify the value that will be accepted by updating directly.
$("#grid1").bind("iggrideditcellending", function (evt, ui) { ui.value = "new value";});
I hope this helps!
Best regards,
Stamen Stoychev
Thx for that wonderful insight! Not sure where that is documented... this is fine I can hold my changes until the ended event.
That brings me down to one issue left, still not able to track down the source of the "sizzle" error.
Ok the issue with 2 is the use of # in my header and data
data
{"AM":"12.13","ROW#":"4.99999","471830.1":0},{"AM":"6.78","ROW#":"4","471830.1":1},{"AM":"3.78","ROW#":"3","471830.1":2},{"AM":"2.11","ROW#":"2","471830.1":3},{"AM":"1.18","ROW#":"1","471830.1":4},{"AM":"0.66","ROW#":"0","471830.1":5}]
header
[{"headerText":"AM","key":"AM","dataType":"string"},{"headerText":"ROW#","key":"ROW#","dataType":"string"},{"headerText":"471830.039174","key":"471830.039174","dataType":"number"}]
This is going to be a bit of an obstacle if we can not use the number char. Is this the case?
Also wanted to comment that I get the same issue ( with auto generate off ) when destroying.
this.gridIDMap.destroy(); <--- gives me that error.
Hi Sean,
This appears to be due to jQuery thinking a new element id is going to be provided. Since jQuery uses the '#' to denote a new ID selector for an element, this is causing problems for jQuery.
If you normally define your own columns, this shouldn't be a problem and when AutoGenerateColumns is enabled it makes its best guess for a column name, which in this case includes the #.
I would recommend defining your own columns to avoid this in the future.
change autoGenerateColumns to true and re-run your script.
I dont recall why I had that in there as I do all my column construction now but that seems to cause the error.
Thank you for the information.
I referenced the same script versions as you have with a simple version of the igGrid using your data. I do not receive the error you are seeing, but my rows do not show until the page is resized in IE10. I also run into this issue when the ROW# column is renamed to remove the "#".
I have attached the sample project I used to test this. Please test this project on your PC and let me know what results you are getting. If you are seeing the same results as usual, this indicates either a problem possibly specific to your environment.
If the sample does show the product feature working correctly, or with rows that are hidden until the windows resizes, this indicates a possible problem in the code of your application. It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing.
Or, if this sample project is not an accurate demonstration of what you're trying to do, please feel free to modify it and send it back, or send a small sample project of your own if you have one.
Please let me know if I can provide any further assistance.
jquery-1.8.2.jsjquery-ui-1.9.1.jsmodernizr-2.5.3.js
infragistics.core.js -- 13.2.20132.2212infragistics.lob.js -- 13.2.20132.2212
The code I had has been changed to fix the bugs discussed here. Though the data going in I provided has not changed. If there is anything you need from my just let me know and ill provided it.