RadDataFilter twoway binding

[Igor]

Hello All

How would I go about doing a bind to a viewmodel with RadDataFilter. The below does not work.

<telerik:RadDataFilter x:Name="JobsFilter" Source="{Binding Jobs}" FilteredSource="{Binding FilteredJobs, Mode=TwoWay, UpdateSourceTrigger=Explicit}" />

[Yoan]

Hi Igor,

Actually, RadDataFilter's FilteredSource property is a ReadOnly one, it has only a getter. You can get its value and return it through a property from your ViewModel, but you cannot bind it.

Regards,
Yoan
Telerik

 

 

[Scott]

Hi Yoan,
How would you go about getting the FilteredSource value from the viewmodel?  I'm trying to use RadDataFilter to filter resources in a ScheduleView control.  My resources are tied to a an appointment list.  Basically I was the user to be able to filter out which staff (resources) they want to see.  The only way I can think to do this is the bind to FilteredSource and update that list of resources, but that is all done in the viewmodel, not the view, so I can't bind anything to FilteredSource in XAML.

[Scott]

I got this working for now, but to do so I broke the MVVM pattern.  Basically I'm listening for the event that fires when the FilterDescriptors change, and I pass in a reference to the View so I can access the DataFilter, then get its FilteredSource and use it accordingly.  I feel like there should be a better way that still adheres to MVVM.

[Yoan]

Hi Scott,

You can check this forum post where a similar question has already been discussed. I believe you will find it useful for your scenario.

Regards,
Yoan
Telerik

 

 

[Scott]

You are correct, that is another way to accomplish what I'm doing, but it still breaks the MVVM pattern by subscribing to an event in the view's code.  My original question was how to do this in a MVVM-friendly way.  I don't know how I could reference the filteredsource in my viewmodel without breaking that pattern.  I'm having trouble binding a property in my VM to filteredsource since it is read only.

[Dimitrina]

Hi,

A possible way to go and keep the MVVM pattern would to use an attached behavior. For more information on attached behaviors you can check the following blog post: MVVM via attached behaviors in Silverlight.

Regards,
Dimitrina
Telerik