When using the "checkBy" attribute to configure the data field for the key definition, then the indeterminate state of parent nodes is broken.
To reproduce the issue have a look to this StackBlitz: https://stackblitz.com/edit/angular-okpokx
Hi Holger,
After performing a review on this issue we came to the conclusion that the demonstrated behavior is expected. A unique field is required so that the check functionality behaves as expected. When checkBy is used there is no guarantee that all items will be checked by a unique field which poses a limitation. Indeed a custom isChecked function should be used for such cases as documented on the following page:
Regards,
Svet
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.