But somehow this "state" must be accessible, as changing pages reveals selected items on any other page.
So if anybody of you is lookin into this as well and can point out where the localStorage of this state can be found, or if you have a workaround for this, I'd be very happy to engage.
If you're interested, this is needed to 'finish' the "Order Summary" (https://blog.jhnr.ch/2016/07/04/advanced-cireson-service-manager-portal-customizations/) feature of my customizations.
Some of the code from this page should help with that: https://community.cireson.com/discussion/comment/839/#Comment_839
Also I think there should/must be a way to get around this without cloning the grid element etc. as the ui element itself can handle it as well ..
Every grid is placed within a <div> with the class 'k-grid'. Well, there you also have the data-attribute 'data-control-valuetargetid'. Its value actually points to a hidden input field residing just on top of that grid-div (duh! should have seen it earlier). This input actually holds the comma separated ids of all selected items for the respective grid.
However, this is not the id you can get from the dataSource.getByUid() method. So you have to get the item from the dataSrc itself. For example like this:
With this I finally was able to fully realize an OrderSummary (Basically a ShoppingCart) for a SR - read more here: https://blog.jhnr.ch/2016/07/04/advanced-cireson-service-manager-portal-customizations/