The whole discussion is becoming complex and I would like to avoid any misunderstanding.
Let me go back one step.

What you cannot do with a DynaMetapushTable or MultiDynaMetapushTable is to filter rows on the client side. These tables show all the rows they receive, according to the items they subscribe to.
Hence, if the item you use on the first page lists all the possible events, you cannot use the same item to feed the second page, where you need to show only a subset of events.

If events A and C are selected, your second page should subscribe to suitable items, like "eventAdetails" and "eventCdetails", that your Data Adapter has to supply. The table is able to show rows from both items.
Then, if the user selects also event E and you want it to appear in the second page, you have to replace the table with a new table which subscribes to "eventAdetails", "eventCdetails" and "eventEdetails".
Is that acceptable?
Otherwise, you must resort to a NonVisualTable.

Your specific scenario is not covered by our examples.
You can see a MultiDynaMetapushTable in the sample installation of Lightstreamer in the Portfolio Demo. The Drop-Down Demo uses a NonVisualTable with COMMAND mode.