Hi Lenon,
You can do several things:
- Make sure Preparation query data is not being used in screen actions without refreshing the query. If you don't do that, the whole query output goes to viewstate, having effect on every AJAX request;
- Avoid Ifs in your Preparation data (read more here);
- Persist information in database instead of session or local variables;
- A good example for that is if you need to upload multiple binaries and you store them in local variables, your screen will be "dead" with so much viewstate. In that scenario, the workaround is to persist the image in the database in a "draft" state;
- Use your session variables wisely and avoid large variables (read more here).
But of course, you may need to have things stores in session variables and having a structure with 2 attributes is the same of having those two attributes as session variables. The algorithm may tell you to avoid records because in theory it is bad but its real-effect is related to the number of attributes in that structure.
Kind Regards,
João