if you use any other scope than a long running conversation or session. On the next request after the clicking someting in the datascroller the data will be gone, due to how scopes work.
And when clicking the datascroller your searchCircuits won't be called again in any case, since it is the outjected listCircuits which the table uses at its data source.
If you really really don't want to use a long running conversation or the session, you can give the a4j:keepAlive component a try.
Thanks for your reply.
What i don't understand is why the PAGE scope is not good for these cases. I was guessing that the datamodel would be created in the page context so the datascroller would have access to the data.