Hello seang,

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

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-gender
Not 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 ?

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.

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.