This surely is a bug in your library. Seems there is an initialization issue, the way i fixed is by checking the collectionchange notification (See attached)

private void DeferAddFilterRow()
{
if (!DataSource.View.IsEmpty)
{
AddFilterRow();
return;
}
DataSource.View.CollectionChanged += DataSourceViewCollectionChanged;
}

private void DataSourceViewCollectionChanged(object sender, NotifyCollectionChangedEventArgs e)
{
if (!DataSource.View.IsEmpty)
{
DataSource.View.CollectionChanged -= DataSourceViewCollectionChanged;
App.Current.Dispatcher.BeginInvoke(new Action(AddFilterRow));
}
}

private void AddFilterRow()
{
grid.FilteringSettings.AllowFiltering = FilterUIType.FilterMenu;
grid.FilteringSettings.FilteringScope = FilteringScope.ColumnLayout;
}

private CollectionViewSource dataSource;
public CollectionViewSource DataSource
{
get { return dataSource; }
set {
dataSource = value;
var binding = new Binding { Source = value };
BindingOperations.SetBinding(grid, XamGrid.ItemsSourceProperty, binding);
DeferAddFilterRow();
}
}

Hi Yanko,

Sorry but didn't understand what do you mean by "checking your progress"r? This is a showstopper and a bug in your library so i had to remove observable collection since xamgrid does not play nice with observable collection (wasted my week of efforts).

Thanks,

Rohit

Hello Rohit,

I am just checking your progress on the issue.

If you require any further assistance please do not hesitate to ask.

Hello Rohit,

I have been looking into your posts and the explained issue is the same referred in the forum thread where you had discussed it with Matt. Currently our development team is working on it.

Let me know, if  you need any other questions on this matter.