We foresee a qvw document containing aggregated data --not real-time. As disaggregation takes place via associative selections a qvw user would narrow down data to the possible lowest level of detail. At this point (and given all choices -saved in Bookmarks or current selections) we want to invoke another qvw to which all the current selections are passed on, triggering --in the process-- a qvd extraction that ensures data is as real-time as feasible (depending on the latency generated by mass data, of course). Is this doable? Your experience and ideas are both welcomed.
Its doable, but chack that your underlying database can handle the query loads. I don't know how many users you have, but the proposed solution will generate multiple reloads during times of the day when your database may already be busy.
A possible alternative is to schedule periodic reloads into one or more qvd's and then daisy chain reloads of the reporting app, so that the document is always as up to date as the schedule you chose allows. Then no user reloads will be required.
Also be aware that Ajax and IE plugin clients (I think) cannot reload documents, so your users would need to use desktop.
Jonathan
Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
