Hi Glenn,

Yes, I tried to duplicate the issue in the sample but was not successful.

Here's our current work around, however, it's not an acceptable solution due to the UI "flicker" caused by collapsing the drop down and then retracting it.  We need a client-side API that does the exact same thing as the workaround please and very, very soon.

oIsCbo.SetSelectedRowByValue(keyValue);
oIsCbo.ShowDropDown();
setTimeout(function() { oIsCbo.SetSelectedIndex(oIsCbo.SelectedIndex);setTimeout(function() { oIsCbo.HideDropDown();}, 200);}, 500);

Essentially we use SetSelectedRowByValue to select by key value which then also sets the correct SelectedIndex on the object.  We then show the drop down, set the selected index and then close the drop down.

If there's any way you can provide that we can manually drill into the WebCombo structure and update the data "under-the-hood" we'd prefer to do that.  This is why I tried the XmlNode which everthing was updated correctly but not posted back for whatever reason.  You probably store the data elsewhere but I can't find where.  It would be helpful if you can provide a "hook" to where we can do this.

If you create a function that's called as your OnColumnSort client-side handler and you try to access columnObject.ColumnMember when it's undefined, your method will crash and therefore crashes the sort routine altogether because the method never returns true.  This is because, as I explained, when called from the context menu, this object's member is undefined.

Creating a simple grid and using the sort isn't sufficient.  Use a simple javascript function like this and then sort using both the column header and the context menu:

    function OnColumnSort(controlId, columnObject)
    {
        alert(columnObject.ColumnMember);
    }

Of course make sure to assign this function to your grid's client side settings.

Hi Andi,

No, you're right.  I was incorrect, the columns are not set to hidden.  Sorry about that.  However, we would like to see the feature where a property specific to exporting would be available so we can include/exclude columns, for export, dynamically even if they're visible.

Our custom row checker/template columns is one example and our trailer column is another.  Thanks Andi.

Thanks Handy.  I've implemented the ResetStatus on the grid client-side initialization and hopefully that will do the trick.

The text setting for customization works like we needed, so thank you for that too.