Query Builder - Parent items are allowing selection when they should not be

[KS]

Hello,

I had a thread about this same issue from a year or two ago, but today I have upgraded to 29.1.33, and I am still seeing the exact same issue.

As you can see below, the parent level elements in the field picker are allowing selection and closing the dropdown, when they should not be. Our setup has remained the same ever since we implemented the QueryBuilder, and this has become an issue after we upgraded to 25.x.xx. It seems to still be a problem in the latest 29.1.33 as well.

I did notice that the parent level elements on the tree within our dropdown do not have the e-prevent class on them, and this seems to be what is needed in order to stop clicking on the parent element from closing the dropdown. If I add that class through the F12 window, then I am seeing it behave properly.

Is there some issue with our setup that is causing this to occur? Would we be able to make sure that the parent level elements can't be selected using a property or something?

Thank you,

KS

[Yohapuja Selvakumaran]

Hi KS,

Thank you for getting back to us and sharing the detailed observations.

We understand that this issue has been persistent since your upgrade to version 25.x.x, and we sincerely appreciate your patience while working through it. We have reviewed the behavior you described — where parent-level elements in the field picker dropdown are incorrectly closing the dropdown when clicked — and tested it using the latest Syncfusion version.

Based on our validation using version 29.2.4, we observed that the parent or group header items in the field picker are not selectable, and clicking on them only expands or collapses the group as expected. The dropdown remains open in this scenario. To help illustrate this, we’ve created a sample for your reference:

Sample:

https://stackblitz.com/edit/angular-5bse6wfx-fhqnwwzs

We recommend updating your project to this latest version (29.2.4) to see if this resolves the issue on your end.

Regarding your observation about the e-prevent class: you’re absolutely right — this class plays a role in preventing the default closing behavior of the dropdown when certain elements are clicked. In our sample and default configuration, this class is automatically applied to parent items to avoid exactly the issue you mentioned. If it’s missing in your setup, there may be a customization or structural difference preventing it from being applied.

To assist you further, we kindly request the following details:

1. Your current QueryBuilder configuration, especially the code related to how the field picker is initialized or customized. This will help us determine whether anything in your implementation might be affecting the default rendering behavior.
2. A short video illustration or screen recording showing how the issue behaves in your application. This will allow us to understand the exact sequence and UI interaction you're encountering.

Once we have these details, we’ll be in a better position to reproduce the issue locally and provide a more tailored solution. We’re committed to resolving this for you and appreciate your help in narrowing it down.

Please let us know if you have any further questions or concerns

Regards,

Yohapuja S