My suggestion is that you look into database theory and normalization instead.
Make two struct tables. One table for team information, one with player information.
Then in the teams table, you put one column down as a unique ID (primary key), and then use that to refer a player to a team in the other table (foreign key).
This gives you the option to pull data from the team, data from a player, or pull all players from the player table, with a specific team ID.
It's basically how databases work, and this can be coded into DashBoard. I currently have about 300 players across 2 leagues and 18 teams in my Dashboard using this system.
------------------------------
Aleksander Stalsberg
Inland Norway University of Applied Sciences/Lillehammer Icehockey Club
Norway
------------------------------