Hi Boris,

_txtAdjustment is a comboeditor control that we just select one of two options that have a numeric value as per the switch options.

PoSModifierItem is a class, the UnitPriceField etc are constant string that hold the names of the fields, hence the names of the columns.

The only part of the program that does not appear to work is where we use the row.Cells["Desc"].Value = ....... and the row.Cells["Desc"].SetValue(...) lines.  Neither line throws an error, but they also do not set the value in the "Desc" column.  The "Desc" column is an unbound column as you can see from the start of the code.

Just to be clear.  What I find confusing is when I use the Init_row method below, the set value on the unbound column works great.

private void _ultraGrid1_InitializeRow(object sender, InitializeRowEventArgs e)
{
    e.Row.Cells["Desc"].Value = e.Row.Cells[PoSModifierItem.DescriptionField].Value;
}

However, when I try to set the value in the button_Click event, it does not receive the new value. 

Are there any limitations of when, or how,  you can assign a value to an unbound column?

Hello,

Could you please review the sample attached to this post and see if it meets your requirements.
Please feel free to let me know if I misunderstood you or if you have any other questions.

I tried your sample, and it did appear to work.  But then I added the missing element, the init_row method, as seen below.  Once this was added, your program does the same as mine, i.e. the valuse do not update when I press the button.  It is almost as if you can only set the value of the unboard cell once?

private void ultraGrid1_InitializeRow(object sender, Infragistics.Win.UltraWinGrid.InitializeRowEventArgs e)
{
    e.Row.Cells["Desc"].Value = "-";
}

Hello townsma,

Actually the value is updating. The reason you could not see it is that the 'InitializeRow' event is firing for every row on clicking the button, because you are changing the values(the records). The value is the overriden with "-". You could put some 'Console.WriteLine()'s or breakpoints to see what I mean.

Please do not hesitate to contact us if you need any additional assistance.

Then surely there is a bug in the control.  The initrow is only supposed to fire when the grid is populated, not everytime a value changes.  If you bind a dataset to the grid, and use a bound column in place of the unbound, it works as expected, i.e. init_row only fires when the grid is populated, and the value in the bound column changes according to the button click.

Surely the firing of events and value setting methods should be the same whether bound or unbound?

Hello townsma,
This was fixed. Were you able to test your application now with the latest service release for 12.1? Please do not hesitate to contact me if you need any additional assistance.

Hello townsma,

I have created the following case for you: 'CAS-86303-KXBXXG' and will update you through it.

Please do not hesitate to contact us if you need any additional assistance.

The InitializeRow event is intended allow you to do things like change the appearance of a row or cell based on a value in that row. Or to perform calculations and populate cell values in the row based on the values of other cells in the same row.

As such, it is supposed to fire initially, the first time the row is created, and also any time any value in any cell of the row is changed.

This is why there is a ReInitialize flag on the event args, so that you know if it's firing for the first time or not.

I agree that the documentation could be a lot clearer, so I think this should be written up as a bug in the documentation so we can get it corrected.

I have read that page, several times recently in fact, and it agrees with me, and I quote.

'This event is generated once for each row being displayed or printed and provides an opportunity to perform actions on the row before it is rendered, such as populating an unbound cell or changing a cell's color based on its value."

It should only fire when the row is initially displayed, i.e grid populated, or repopulated. It should not fire because I change the value of a single unbound cell in code. 

I have been using UltraWinGrid since it was still called Sheriden Grid.  I know when these events are supposed to fire, and changing the value of any cell using code is not supposed to re-initialize the row.

I have implemented the work around to check if this is a re-init as opposed to the initial init, and it solves my immediate problem.  However, I should not need to do that, so I suggest you pass this along to the developers, as this is a bug, whether you wish to admit it or not.