Apparently Grid/TreeGrid components do not behave that well when the underlying datasource changes especially with regard to the move/remove item operations.

In particular, regarding JCR domain with the fragile session-dependent nodes, Grid/TreeGrid might blow up with exceptions:

• Remove a node in one Admincentral session, click it in the other session open in a different tab - Grid will try to refresh the ids of the items (including the deleted ones) and causes a repo exception.

Related logic is located in e.g. DataCommunicator.ActiveDataHandler and DataKeyMapper - those are responsible for keeping mapping information between client-side ids vs the domain items (nodes in this case).

Clearing out stale/no longer existing nodes is tedious - for that we have to override DataCommunicator and HierarchyMapper (for the flat Grid).