CollectionViewSource sorting only the first time it is bound to a source by Mischiew

The work around by Greg Bachraty does not "Cut" the code by overriding the metadata. Overriding does not change the behavior of the parent class and the OnCoerceItemsSourceProperty method is still called (Clearing the items Sorts/ Group).

Therefore that workaround will not prevent this issue.

The WPF team has recently reviewed this issue and will not be addressing this issue as at this time the team is focusing on the bugs impacting the highest number of WPF developers. If you believe that this was resolved in error, please reactivate this bug with any necessary supporting details.

We appreciate the feedback. However, this issue will not be addressed in the next version of WPF. Thank you.
–WPF Team.

Added another workaround for this that seems to work fine.

After all this time there's still no fix for this?

It's verified all over the place, including StackOverflow.

Thanks MS for the good support. Bottom line, don't use the DataGrid...

I feel your pain. I've been scratching my head for a viable workaround for days now. Bugs like this are the reason WPF is still not ready for production-quality business apps even though WinForms data binding is far from perfect.

Feedback would be welcome, will this bug be fixed one day?
The DataGrid is still pretty much unstable, it would be good to know whether to use it at all in current applications.

Any progress on this bug?

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

The error is in the DataGrid. If I'm using a ListBox instead of a DataGrid, the problem disappears. If I'm using a DataGrid and a ListBox (to double-check), then the problem is back (see commented code in MainWindow.xaml).

The source of the problem is most likely this one in the DataGrid sources:

1) in the static constructor:

ItemsSourceProperty.OverrideMetadata(ownerType, new FrameworkPropertyMetadata((PropertyChangedCallback)null, OnCoerceItemsSourceProperty));

2) lower:

        /// <summary>
        ///     Coercion callback for ItemsSource property
        /// </summary>
        /// <remarks>
        ///     SortDescriptions and GroupDescriptions are supposed to be
        ///     cleared in PropertyChangedCallback or OnItemsSourceChanged
        ///     virtual. But it seems that the SortDescriptions are applied
        ///     to the new CollectionView due to new ItemsSource in
        ///     PropertyChangedCallback of base class (which would execute
        ///     before PropertyChangedCallback of this class) and before calling
        ///     OnItemsSourceChanged virtual. Hence handling it in Coercion callback.
        /// </remarks>
        private static object OnCoerceItemsSourceProperty(DependencyObject d, object baseValue)
        {
            DataGrid dataGrid = (DataGrid)d;
            if (baseValue != dataGrid._cachedItemsSource && dataGrid._cachedItemsSource != null)
            {
                dataGrid.ClearSortDescriptionsOnItemsSourceChange();
            }

            return baseValue;
        }


If the descriptions are removed, clearly it will break up everything each time another source is selected!

As one can see in the MainWindow.xaml.cs file, I've tried a workaround to save and replace the SortDescription items in the CollectionView, but while this fixes the displayed order, it breaks the keyboard nivagation and it is not possible anymore to use the up/down key to get to all the items (stays stuck on some of them).