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.

thx Michael, thanks for the info.

So I've been following this thread for a while and I am thoroughly confused.  I have no clue what you are trying to do because your screenshot doesn't match the sample JS code you posted and it is littered with errors.  Infragistics won't ever admit to this or speak openly about sloppy code but I am not associated with them so I'll speak freely.

- In any development shop whether IT or software, if you upgrade software and encounter issues, you immediately roll it back.  You have not stated why you chose to upgrade even if it was necessary for either new functionality or fixes to blocking bugs.  That being said, why are you guys upgrading?  It seems to be doing more harm than good.  Obviously Infragistics wants their customers to upgrade but it is not always a simple task as you've encountered.

- From looking at the screenshot, I presume you are creating a matrix of sorts.  Between using ColumnFixing and FixedHeaders you should be able to achieve your end result pretty easily. 

- I don't agree with how you are performing your edits.  It seems over complicated.  Here is what I see:

1. Headers are sorted from lowest to highest.
2. 1st row column is sorted from highest to lowest.
3. 1st row column is read-only with same styling as header.
4. The intersection is the value within the matrix.

I prefer setting the option on the grid to autoCommit: true.  This way it will update your data source directly without having to mess with a transaction log.  Not only that, you can easily get the values of each row without figuring out which cell was selected. 

I can provide samples if you would like to see this implementation.

- The primary key issue is your issue.  You introduced it probably for no reason.  In most cases, you should not be editing a primary key.  Instead, create a (hidden) column in your grid and assign that to your primary key.  If you must edit the primary key, then in your data source create another column just for a client side key.  That way the grid will not get confused on which row is being edited because the underlying key was changed.  To add a new property simple loop through data source and create a new property and assign a number to each row.  It's that simple.  When you save this back to your database, you simply ignore this field. 

I can provide samples on this as well.

- You mentioned that you update cells by getting the innerHTML which is a little absurd.  Let the grid handle it unless you are providing additional business logic to the updates. 

I can provide a sample on this as well if you like.

- Lastly, your primary question was why is there a box hovering around the grid when you enter edit mode.  Honestly, this is a CSS issue.  If you are using templates from ThemeRoller, I'd try to update it to a new version.  Otherwise I'd use the base theme to see if it goes away before you try anything else.  If you made changes to the CSS files from the OLD version of Infragistics, then those were overridden because you upgraded to a new version.  Check source control and see if anyone made specific changes to any CSS files before you performed an upgrade.  Also use Fiddler to ensure that all files are being loaded correctly and that you aren't experiencing any 404 errors.

We've created some pretty crazy grids here using their Ignite UI.  It has handled just about everything we threw at it.  I've never created a matrix before but I am certain we would be able to do it pretty easily.  I'd be more than happy to help you out if you want.  We would just need a bit more information to get that jump started.  Its been a month but I'll help to try to get this one solved.

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.

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.

Hi seang,

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.js
jquery-ui-1.9.1.js
modernizr-2.5.3.js

infragistics.core.js -- 13.2.20132.2212
infragistics.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.