Hi Rayko,

During an additional revision of this item with the development team, we've confirmed that the reported behavior is not a bug with the component but an expected functioning. Let me provide more details.

The issue occurs when one is using a custom component inside the FilterTemplate and setting the filter value in the custom component when it initializes. Based on how the framework operates, this custom component inside the FilterTemplate will be initialized first before the Grid. The Grid then initializes and sets the filtered state but the custom component in the FilterTemplate is not refreshed to show the new value.

To refresh it in this case, we will need to re-render the whole Grid which will have non-desired performance implications. The behavior has changed after 5.1.1 due to performance optimizations in the Grid striving to not rerender it when not needed.

The recommended approach is to set the filter value upon parameters set and not when the custom component in the FilterTemplate initializes.

So, in the CustomTextRowFilter component inside the FilterTemplate, instead of overriding the OnInitializedAsync to set the filters:

        protected override Task OnInitializedAsync()
        {
            Field = ((FilterDescriptor)Context.FilterDescriptor.FilterDescriptors[0])?.Member;
            SetValue(((FilterDescriptor)Context.FilterDescriptor.FilterDescriptors[0]).Value);
            SetOperator();
            return base.OnInitializedAsync();
        }

set them in OnParametersSetAsync:

        protected override Task OnParametersSetAsync()
        {
            Field = ((FilterDescriptor)Context.FilterDescriptor.FilterDescriptors[0])?.Member;
            SetValue(((FilterDescriptor)Context.FilterDescriptor.FilterDescriptors[0]).Value);
            SetOperator();
            return base.OnParametersSetAsync();
        }

Having the above in mind, I am hereby marking the item as "Won't Fix" as the described behavior is expected.

Regards,
Nadezhda Tacheva
Progress Telerik