Regarding iViews closing

Question

Hi Experts,
I would like to get some clarifications.
We have a dashboard with 5-7 iviews. Result set is one of that. We tried avoiding the inital load to the result set since we have around 200000 records. we failed in getting that.  Now the clerification points are
1. Is there a way to avoid initial loading
2. If we are making on the iview collpased in property for resultset, would this avoid loading at start up? or still the data is loading and then its collapsed? i.e. same transaction time, same memory will be used?
Kindly hele me understanding or refer some materials.
thanks,
SK

Answer 1

Hi SK,
  If I'm following your description correctly, you offer 5 iViews anchored to single page/role and all iViews are loaded simultaneously at runtime. This simultaneous loading is what you're trying to avoid and you'd rather the iViews (data) remained collapsed until a user clicks them. Correct?
  If so, this fix may be more simple than you think. If you just "push" your iViews to the detailed navigation area of the role, you'll achieve what you want. You can do this many ways but the easiest would be to make sure your role is an entry point, this ensures it appears in TLN. Then add a folder at the root level of the role and give it some name since this name will be seen in 2nd level navigation. Place your iviews in that folder, this ensures they appear in DTN.
  In this scenario, the first iView in the list will be shown when the role is called at runtime. However, if you want them all to remain "inactive" until clicked, you could always add a "Workset Map iView" as the first entry in the folder, before your iViews. This way, when the role is called at runtime, the folder name appears in 2nd level and the workset map iView is called whichi will simply display a list of the 5 iViews in the portal content area with a generic icon (which is customizable). When a user clicks one of those, the report runs, but not until.
Is that what you meant? If not, let me know.
-Kevin