bdelmee wrote:Item source/default values affect the items as rendered on the page, not in session state (you can see this by using the Session viewer when the page is first rendered). To set values in both the rendered items and session state, set the initial values using computations or processes rather than item source/default attributes.
I am probably missing something obvious here, but select list on a page are correctly displayed (using the underlying static llist or query), and the default value (static while testing) is displayed, yet it seems that on the very first invocation, the page items are not known on the server-side. Hence report/graph regions that use the items as parameters return 'no data found'. If I submit all works as expected (either through a button, an item change or merely by clicking the tab that displays this page for a 2d time). How do I ensure that the value initially displayed/selected is actually set a the page scope as well?
bdelmee wrote:Stating the obvious: Did you try logging out and logging back in to start a new session?
Thanks, I suspected something like that, and have actually tried a computation "On New Instance (new session)" -since I do not want to override the user's selection all the time, just initially- but it does not seem to do anything at all. I've used the debugger "session" button which shows the items as unset indeed...