Has anyone had any particular issues with using session.custom to store values that are used between views and/or any pitfalls / issues with using session.custom things to avoid or works really well for x.
Not asking for anything in particular on my end currently.
I've had good luck using them to provide "global" variables to all the session's views.
Also use them for project level variables I want to have in one place.
The biggest issue at the moment is the bug that causes the entire session.custom props to just disappear randomly while you’re in the designer, without your knowledge, and then you go to save and now it’s propagated to the live system. It’s extremely important to have regular backups of these props so that you can reimport them in a few minutes rather than a few hours/days.
Other than that, the other issue is organisation of them. You might want to use them for specific Views to store data that you don’t want lost when the user navigates away from the View and then come back again. You need a good organisation structure to store data like this, as you could potentially end up with lots of Views that need this.
That being said, they’re incredibly useful
Edit: just remember that they are session-wide. If a user has multiple tabs open to the Perspective client, they all run under the same session. This is either useful or not. For navigation or selection of things that are page-based, this is not useful. This is where Phil’s Integration Toolkit’s (wiki) pageVarMap is useful
have you had any issues with size / amount of data in the session.custom causing issues with responsiveness or memory usage?
Not in my experience, although I've never housed anything large in there myself