Graphics

New here so this has probably been covered, but I'll post anyway.

I have used crossfire in the past to pull season stats for baseball from Statcrew to graphics. But I want to switch to Xpression this season. The problem I'm encountering is that Statcrew organizes season stats in batting order. So one day the 1 hole player might be jersey 5, but the next day it might be #10. So if I link my premade graphics one game and then they will be totally off the next game if our batting order changes. I'm pretty beginner at Xpression, but the one solution I have found so far would be to set up datalinq keys to change a graphics player identity, name, jersey, picture, etc. And just have 9 graphics or so with the stats linked to the batting order. And then before games I just look at order and change my jersey # key so it matches whoever is in that specific spot in the order.

This doesn't seem like the perfect solution since when a new batter comes in, say in the 2 hole, it will push everyone down a spot in Statcrew so I will have to go and move my order down a spot in Xpression. Maybe there is just a totally easier way to do this.

Would love some tips, thanks everyone!

I'm in basketball but your plan makes total sense to me. I was thinking if you made a dashboard you would just have to enter the lineup by jersey number and then the datalinq keys would go find all the stats. You could also link headshots to populate automatically. (maybe an excel sheet here)
#XPression

When you are doing your datalinq query, typically the column line will look something like this: /player, /player<2>, /player<3>, etc and will have a child under it called something like jersey_num or number. To ensure that you are finding the correct player, you can do a query within those arrows. Say you set up a datalinq key called "jersey". Whenever you set up your datalinq, in the column line you would want to set the query up something like so: /player. In this case, you are telling datalinq to find the right column in which the child node (number, jersey_num, etc) is equal to your datalinq key (%jersey%). So whatever you type in as your datalinq key, say jersey 21, datalinq will only look for the stats associated with the child node = 21. Hope this all makes sense.
#XPression

It may not be required for Statcrew, but I'll throw this tip out for others reading this thread.

In more advanced cases, you can actually search for multiple elements as well.. Image a case where players for both teams were in the same XML element list and you need to search for a certain player on a specific team.
Example: /player/

and if the jersey number were in a child element beneath you can search for that too. Image it were something like this

<players>
  <player>
    <info>
      <jersey>10</jersey>
    </info>
    <stats avg="0.356">
    </stat>
  </player>
....
</players>

You could use /players/player/stats/

#XPression