We use report controls extensively in our applications (probably more than 20 in each) and we recently upgraded from XTP 15.2.1 to 15.2.1.0403 to address a crash when dragging a grouped field onto the report. However we almost immediately began noticing very strange behavior all over our application. It turns out that each time we load data into the report control, an item is now auto-selected. Since we often respond to a user selection of data, we had the application going crazy and selecting things by itself all over the place in response to Populate calls as we often show subdetails from one item in a second report, and their children in a third. We don't want a cascading effect if the user is not actually physically clicking on the row.

Here is the new piece of code inserted after the initial release of 15.2.1 at the end of CXTPReportControl::Populate(). 

if (GetBehavior()->Notifications->Populate->bSelectionChanged)
{
   if (m_pSelectedRows->IsChanged())
   {
      OnSelectionChanged();
      m_pSelectedRows->SetChanged(FALSE);
   }
}

We are not sure why this new piece of code is here. There doesn't seem to be any mention of this in the release notes. Is this a new feature?. Why is the default behavior now to send a selection changed message on populate? The CXTPReportBehavior class is not even documented. I suppose we can go to each of our report controls and set the bSelectionChanged variable to false, but would it not make more sense that this should be false by default if this makes such a big change in behavior?

For now we are thinking of rolling back to the initial 15.2.1 release and live with the bugs that the hotfix resolves rather than trying to patch this new behavior and possibly miss some cases.

Derek

We seem to have found a solution which we are testing. We call the following on the CXTPReportControl item and this seems to prevent auto-selection.