Thanks for the lead. I've never even seen the SDK before.
The merge method looks promising...will have to experiment. Is there additional documentation on the classes in the SDK (examples, etc.) that would include the PropertyTree class?
If I understand you correctly, you're suggesting I create custom properties on the session object and then bind the relevant view component properties to the custom session properties. That would keep user preferences sticky during a session, but then they'd lose them on a new session - correct?
The app we're building will have a number of different tables that users will customize (e.g. filters, columns shown/hidden, column order, width, etc.) based on their role and location, shift, coverage area, etc. In some cases we can derive this from user data, but there's also a lot of personal preference going on and we want to provide users with a way of saving a snapshot of their customizations. We don't want them to have to go through all the clicks to restore their customizations every time they start a new session.
Maybe it's easier to save & restore the session custom properties to a DB than each of the table properties?