Duplicating Players (answered)

[bepeacock]

I purchased the roster add-on, as I do each year happily, and at the season opener of my local MiLB team, I imported the rosters as usual. But there were several players missing so I had to manually add subs throughout the game. Now I'm setting up to go to another game and updated the rosters with Discover. It has duplicated all the players I manually entered. So I merged them all. Updated rosters again, and they duplicated again. How can I prevent this? What am I doing wrong?

[OhioTex]

My guess is when you merged .. You merge "the wrong direction"

When you discover a team ( and players) the program assigns a unique Id inside the program code to the team and players . When you merge you need to make sure "the discovered teams" are the ones that 'survive' so the internal identifier is not lost

Re try the merge and make sure the "direction" of merge is correct

( let us know if that fixes it)

[Jaskegreen]

Here is another scenario. I have imported teams from MaxPreps into my iPad. I've been scoring my son's games since he has been 9 (now 16) and have never seen this issue before.

I haven't been able to make a couple of his high school games on time, so I have another dad who scores those games with iScore. After the game, he and I try to share the game from his iPad to mine. During the process, iScore wants to send me both teams and all players which I already have. I okayed it once before which duplicated the teams and all players to my iPad which I had to merge each one (boy that was fun!).

I know it wants to import teams and players because it has a blue arrow under both teams and all players when at the confirmation screen. Is there anyway to Data Share this info without duplicating?

[FTMSupport]

If the other person scoring the games also imports teams from MaxPreps, then the internal IDs of the players will be the same, and no "mapping" will be required. If they are creating the players manually, then iScore will ask you to either map the players, or if they have been mapped in the past, it will remember the past mapping and not allow you to select a new one.

[Jaskegreen]

The other dad did import the teams from MaxPreps as well. So I see on the Map Data screen it says Team Mapping with both teams underneath. Also team players for each team under that. If I "verify" the import from Data Sharing, it should map and not duplicate. This is the process I went through for the prior game I imported from him.

I'm going to hit verify and pray I don't have to Import to revert the database. Thanks for the reply.

UPDATE: It worked! So I guess the players that were duplicated the first time I did a Data Share were not from the MaxPreps import.

[OhioTex]

@jaskegreen .. Yes you have been a long time Iscore user for many a year.. Hope your son HS years are going well..

Been there before ...Painful to have to find and keep straight and merge players post a data share when mapping is not clean.

A small trick that helps me some ....when for various reasons internal identifiers get crossed up and I can see proposed mapping likely not going to be clean ... I Try and create and turn on a new temporary "transfer in" league, before a potentially messy incoming data share. So players and team that comes in can be easily identified with leagues filter. So if I do have to merge players, this can reduce the amount of searching and scrolling in player manager. It also helps me identify which duplicate should survive and which should be merged away.

A small help.. But still painful when inbound mapping gets confused

[Jaskegreen]

Thanks @OhioTex. Nice to hear from you again, and hope all is well with you. Thanks for the tips.

[photojon]

Following up on this thread with a question about the "scope" of Leagues. I use Leagues to keep track of tournament stats for every tournament we have been in for the last 7 years is a league. When I find duplicate players, I have been merging them independent of what League they were created in. My "ideal use model" would be to have "all players" in "all leagues" from a reference above, I am concerned that by merging the "same player" from "different leagues" that I might be causing a problem down the road. Is there a way I can "select all" players and assign them to "all leagues"?

Another reference at the top of the thread mentions "internal ids". Many of the players we face have been around for most of the 7 years if scored, and most of them have played on many different teams over the years. When I "discover a team" using the USSSA team ID, will that import attempt to find a player with a matching name in my "Player Manager"? Before "discover" was an option, I entered everything manually. I'm just trying to figure out if discovering teams in this manner is going to continually duplicate players.

Thanks!

[OhioTex]

@ photoJohn - nice to see you back on the forum. I saw a few posts earlier in the month but none over the summer. glad to see you are still at it.

when merging players, unfortunately, you can easily loose league associations of a player on the "right" side of the merge.
as you know the player on left side of the merge "survives" . as do his leagues. but not same for right side player. the leagues 'left guy" had going in is who the combined player has coming out. if player on right side had different leagues assigned... lost. right guy ends up with what left side had to begin with.

Over the years my player to league assignments have not held up well, and like you pointed out in other posts, with thousands, unwieldy. I have pretty much resigned myself to all players in ALL league and not manage the players in individual leagues, unless my team. when playing players from prior years, i either have to do the painstaking process of adding them in one by one or loose the historical completeness.


as I understand it. USSSA has its own internal ID. it will not understand your original manual ID. . but if you discover a USSSA player and then merge him with the USSSA ID player on the left and your manual original player on the right, your combined player will inherit the USSSA ID for later