Thank you for your help.

I have tried to use the above given workaround but it is not working in my case, as I have provided you with the format which I am using and I have tried to use the following workaround:

 function HandleExitEdit(gridID,cellID)
  {
        var cell                  = igtbl_getCellById(cellID);
        var line                 = cell.getRow().getIndex();
        var rows               = igtbl_getGridById(gridID).Rows;
        var current_line  = rows.getRow(line);
        var coluna           = cell.Column.Key;
  
   if ((coluna == 'TestCol') && (current_line.getCellFromKey('TestCol').getValue() != "")&& (current_line.getCellFromKey('TestCol').getValue() != null))
   {
             var value = current_line.getCellFromKey('TestCol').getValue();

            //Type here a piece of code to format the string
             value = parseFloat(value) / 1000;            
// But this will change the column value + this will need to interchange when again try to access the //column Please suggest do I need to set column format from there??
          current_line.getCellFromKey('TestCol').setValue(value);
         
   }
  }

Bunty :)

still there is no update ?????

I'm having the same problem as the original poster.  I have a column with a mask of "#,###,###".  The column has decimal data.  If a cell has a value of 90.5 when bound to the datasource, it is correctly formatted, rounded, and displayed as 91.

HOWEVER, if I use the cell.setValue() method to set the same cell to 90.5, the setValue() method incorrectly applies the format and displays a value of 90.  If the data is saved and the grid re-bound, the grid correctly displays 91.  In my case, the user makes an edit to a column which updates another calculated column.  However, the calculated value displayed is wrong because of this rounding error until they save and the refresh the grid.

The supposed work around above to format the data before calling setValue is unacceptable.  That would change the actual data value.  Continuing with the above example, I don't want to save the value 91.  I need to save 90.5, and just have it display 91 (which is what it does correctly when the bound data is formatted initially).

Contrary to the post above, setValue() does NOT correctly apply the format if one already exists on the column.  It partially applies the format, but rounding is not handled appropriately.

At this point, the only work arounds I can come up with is to have another hidden column with the actual calculated value and then format the display value in a separate displayed column or to redo the calculations on the server side before saving the data.  Both of these options are, of course, absurd.  I shouldn't have to do this.  The infragistics setValue() method should use the column's formatting and should round correctly, but it just doesn't.  This appears to be a bug.