Thank you for suggestion. But I am talking about InitializeGroupByRow not InitializeRow. But the time  InitializeGroupByRow is fired everything theoretically should be in place.

However, I will be happy to re-scroll  when the grid is totally initialized. Do you know how can I identify that the grid is initialized? I was trying to re-scroll after the UltraDataSource is completly updated (the grid is more or less static from the point of the data), but by this time Grid was not ready: the  GroupBy rows have not been created yet.

This is probably a timing issue. The grid is probably scrolling based on the positon of the BindingManager, and this occurs after InitializeGroupByRow has fired. 

There's really no way to determine when the Initialization is "done" since it's asynchronous. What I would do is... immediately after you set the DataSource and DataMember on the grid (or call SetDataBinding), use BeginInvoke to call a method that scrolls the row you want into view. The BeginInvoke should cause enough delay for the grid to finish up whatever it was doing. 

Make

Thank you  for advice. DataSource is set at the design time with UltraDataSource. My grid initialisation routine called from Form_Load is simply reading from DB row-by-row and adding rows to UltraDataSource with BeginUpdate() and SuspendRowSynchronization() at the start and ResumeRowSynchronization()/EndUpdate() in finally.

I have tried to call BeginInvoke for scrolling after this function. It didn't help due to the fact that the grid is initialising: I am receiving exception

"Invoke or BeginInvoke cannot be called on a control until the window handle has been created"

However, I do not believe it is  timing. I have seen scrolling working in InitializeGroupByRow (with debugger breakpoint right after the needed row was scrolled). But sometime nearer to the end of Grid update, grid just restores original scroll order (maybe by clearing ActiveRowScrollRegion? or something like this).

Normal 0 false false false MicrosoftInternetExplorer4

Did you manage to solve this issue as there seems to be several of us who are suffering from the same issue here, although no-one has really helped to resolve this issue,. I'd be keen to know if Infragistics have accepted that this functionality simply doesn’t work.

The whole process doesn’t seem to have been very well thought out, especially when it comes to setting scroll-bar positioning in a group-by situation.

Kind of

 private void ultraGridBacktest_InitializeGroupByRow(RowsCollection rows, UltraGridRow row)

{

     foreach (UltraGridRow row in e.Row.Rows)

       {

                    this.BeginInvoke(new UpdateFixRowStatusHandle(UpdateFixRowStatus), new object[] {e.Row.Rows, row})

        }

}

        private void UpdateFixRowStatus(RowsCollection rows, UltraGridRow row, bool fixedRow)
        {
            try
            {
                if (row.VisibleIndex >= 0)
                {
                    if (fixedRow)
                    {
                        if (!rows.FixedRows.Contains(row))
                        {
                            row.Fixed = true;                           
                        }
                    }
                    else
                    {
                        if (rows.FixedRows.Contains(row))
                        {
                           
                            row.Fixed = false;                                                       
                            ultraGrid.DisplayLayout.RowScrollRegions[0].Scroll(RowScrollAction.LineUp);
                        }
                    }

                    //reload order
                    row.RefreshSortPosition();
                   
                }
               
            }
            catch(Exception ex)
            {
              
            }
        
        }

   This code essentially moves the grid one line up in certain  conditions that make row visible. But I do not remember details. Above is extract from my code. Hope it helps.