You can actually take this a step further if you have Xpression v9 or above now...
When you set the DataLinq Properties, the window has changed slightly now, and you have a few more information fields and a few more options.

Specifically the support of the @TextObject@ macro and the "Requery scene datalinqs on data change" option.
Now, the solution above explained by Wes works perfectly for anyone working from Xpression and using the sequencer like that.
However, in my case I'm trying to get this as efficient as possible from a simplified user interface, and then DashBoard comes into mind quite easily. I also try to make as many "templates" as possible, leaving out the need for several, if not hundreds of entries in the sequencer.
Using the examples from above, and combining them with DashBoard and data from the DashBoard, you can in theory make one template with just one entry in the sequencer, and then have a scene where you show all the information from an Excel sheet (ADODB style), but you can choose the player with a single jersey entry parameter in DashBoard, and you can have the entire scene populate with the correct information.
Information that can, in theory, be worked on by a third party live as you call data from it.
It will get the row data based on what jersey number is picked, and the jersey number is set in DashBoard.
Here is where you check the "Re-query scene datalinqs on change", meaning every time the jersey number changes from DashBoard, the other data is also re-queried from the Excel sheet.
Voila, you've just married two DataLinq sources in one and you can finally pick the player jersey and corresponding collumns in Excel through DashBoard.
So finally, you can do what Grenier said was messy two years ago (and it really was back then).
#XPression