Hi all,

Thank you for your feedback! I've shared it with the team for consideration.

As for the column chooser, we do see value in exposing it as a separate component that can be used outside of the column level. That said, I opened a dedicated feature request on the matter:

Standalone ColumnChooser component

I opened it on Thomas's behalf as he first raised the topic. However, I added both Thomas's and Michal's votes as community members who expressed interest in this feature.

Please feel free to share any other feedback and expectations for the behavior and design of such a component in the dedicated post. For example, in both of the demos Michal shared the Grid allows opening the ColumnChooser from a button in the Toolbar. The ColumnChooser itself is rendered in a popup where the column visibility is controlled by CheckBoxes. However, in one of the demos I see that it is also possible to reorder the columns from the ColumnChooser.

It will also be useful if you can share how you'd prefer such component to be exposed - for example, on Grid level or outside of the Grid similar to the Filter component and how it can be integrated.

Sharing your vision is important to us as thus we can ensure we are meeting the community requirements. Thank you once again for being valuable members of the UI for Blazor community!

Regards,
Nadezhda Tacheva
Progress Telerik

Hi all,

The suggested approach is a workaround option that can be used if the use case requires a Filter Row to work with Column Menu. However, as per the Grid design at this stage, the Column Menu can be used only with Filter Menu. In this scenario, Filter Row is not supported since it uses different type of FilterDescriptors.

We are considering two options for the implementation. It will be useful if you can share your feedback, so we can ensure we are meeting the community requirements. Listing the possibilities here as well:

• Option 1: Support Column Menu without Filter Menu but with Filter Row. In this case, the two filtering options will continue to use different filter descriptors but the Column Menu will be configured to support Filter Row with FilterDescriptors. Currently, it uses Filter Menu with CompositeFilterDescriptors. This, however, would mean that the Column Menu will no longer support Filter Menu, so please take that into consideration.
  
  
• Option 2: Configure the Filter Row mode to also use CompositeFilterDescriptor. Such an option would be a breaking change and could be targeted no earlier than UI for Blazor 4.0.0.

Apart from that, it is important to vote for the request since we are prioritizing such enhancements based on the community demand. I see that Dennis's vote was missing, so I added it. You may also subscribe for the item, so you will receive status updates. This is the best way to follow the progress of the feature.

Regards,
Nadezhda Tacheva
Progress Telerik

Hi Thomas,

Once the ColumnMenu is enabled, the Grid is prepared to work with FilterMenu. Even if you disable the filtering through the GridColumnMenuSettings and enable FilterRow on Grid level, the component still expects CompositeFilterDescriptor while the FilterRow works with FilterDescriptor. You can explore the difference in this Filter Descriptors section.

By the time the enhancement is implemented, you may try using the approach that Michal suggested (example link listed in my previous post) - toggling the ColumnMenu, so you can use the FilterRow when the menu is disabled.

Regards,
Nadezhda Tacheva
Progress Telerik

Hi Michal,

At this stage, the two filter modes still operate with different filter decriptors and therefore a custom approach should be used until the enhancement is live.

There are multiple options that one can accommodate based on the specific scenario. The solution you have chosen is one way to proceed. I have tested it with the latest version of Telerik UI for Blazor (currently 3.1.0) but changing the FilterMode at runtime does not seem to cause any issues on my side. Here is a runnable version of the replicated scenario - https://blazorrepl.telerik.com/cmaeYhbv13vG4jw444. You can test it and compare it to your configuration to see what might be missing. If you are still experiencing issues, you can open a dedicated ticket, so we can evaluate the use case there.

Regards,
Nadezhda Tacheva
Progress Telerik

Hi Korstiaan,

Having in mind the different essence of the Angular/Jquery and Blazor, the implementation of the components and features for the corresponding suites is also distinct. So, some differences may be observed in the behavior of the various components, as for example in this case. In the Blazor Grid, both of the filter modes use separate descriptors at this stage.

As mentioned in my previous post, one of the options we are considering is unifying the filter descriptors, so both Filter Menu and Filter Row use CompositeFilterDescriptor.

That being said, thank you for providing detailed feedback on your expectations for this feature. It is valuable and will be taken into consideration once the discussions for its implementation are initiated.

Regards,
Nadezhda Tacheva
Progress Telerik

Hello Korstiaan,

By design of the Grid for Blazor, its Filter menu uses CompositeFilterDescriptors, while its Filter Row uses FilterDescriptors. Since the filter descriptors of the two modes are different they cannot work together and thus the Column menu which provides Filter menu option is not compatible with Filter Row.

As I consider allowing compatibility of Filter Row with Column menu a reasonable feature request, I raised a discussion with the development team to revise what would be the options for such implementation. At this stage we are considering a couple of approaches as follows:

• Support Column Menu without Filter Menu but with Filter Row. The main goal here is to avoid having two filter types because the conflict comes from the different filter descriptors they use.
  
  
• Configure the Filter Row mode to also use CompositeFilterDescriptor. Such an option would be a breaking change.

Feel free to share your thoughts on how you would expect this functionality to behave. It will be very helpful for us to see the vision of our community for possible implementation.

In the meantime, I added your vote to increase the popularity of the request as we are prioritizing the feature requests implementation based on the community interest and demand. As you are the creator of the post, you are subscribed and will receive email notifications when its status changes. This is the best way to keep in track with the progress of the feature as once we know which release will contain its implementation, we will update its status in the feedback portal and you will be notified via email accordingly.

I hope you will find the above information useful. If any further questions appear, please let us know.

Regards,
Nadezhda Tacheva
Progress Telerik