Grigas

This is an interesting problem... As I mentioned earlier, filtering is being performed on the backend against the created hierarchy. The "Not specified" label is assigned to nodes that don't...

FWIW, I filed [an issue](https://github.com/iTwin/presentation/issues/389) in our backlog to make sure we support this situation in the new hierarchies builder implementation we've been working on lately.

> @1abjora @grigasp Any news on this one? Maybe this could be scheduled for upcoming future? Or we could make a contribution that enables custom processing of current rules (minimal...

Tree widget version 3.x doesn't use rulesets any more, so requirements need to be revisited in the changed context. Closing this issue, please open a new one if any improvements...

**Just to make it clear, the suggestion applies both - to properties in property grid and to nodes in tree component.** I believe accessing context menu through a right click...

Deadlock call stack: 

The fix was released with `itwinjs-core` packages `@4.6.1`

> @grigasp We're still able to reproduce this issue with Core 4.6.1 Are you seeing a hang or a slowdown with this version?

> We got a hang for 10 min for the whole app. After that, properties grid stopped loading properties and we started to get BackendTimeout continuously Any chance you could...

> Something like this would help? But on our app process, not system as mentioned in the link > > https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/task-manager-live-dump Not sure if the ones created through task manager...