What you are suggesting sounds viable, although I have never tried it.
What I generally do for a mashup is a create dedicated qvf app for it. So maybe you could create a single qvf app that contains the data your mashup needs, as opposed to trying to sync several qvf data source apps. This may sound a bit of a palaver but I reckon would be quicker to do and end up with a more efficient and reliable mashup.
I have done some work on this. Some recommendations:
- use one app as a master app, where the user makes selections in the common fields
- listen to the selections with List objects, created with createList
- propagate the selections to the other apps with field.select
Hope you find this helpful
Thanks again for the tips!
Using the createList method was clearly a better idea than dealing with the whole CurrentSelections object.
In the end I only had to propagate selections on a defined user action so I used createList to get selections, field.select to apply them and destroyed the list object in the end.