Like many people at the moment, I'm going through old scorecards and correcting the cards where player's retirements were not correctly entered. Unfortunately for old scorecards, the amount of work required is quite laborious, as the options for entering the batter's name (in the retired section) are restricted to those that are listed in the current team. This obviously works well for recent scorecard, but doesn't work for old cards where players are long retired. I have to find the player who retired, go into players, activate the player, go into teams, add the player into the correct team, then make the change to the scorecard, then remove the player from the correct team, and then deactivate the player. Am I doing it correctly? Is there an easier way of doing things? For instance, should all partnership fields be limited to the batters that have been listed in the innings? (We can move this to Suggestions if this is the case)
Morning Mark. Everything is working perfectly
@Paul Reynolds (or anyone) How is this new system working for you?
Thanks Mark, I thought as much. Unfortunately some tams are not as conscious and careful when entering scorecards, and in a lot of cases it will be the opposition entering their batting card and don't give a toss about entering our fielders in. No worries, I'll have to stay with the old fashioned very manual method.
Hi Mark, slightly different scenario, but it I'll add here as it has a similar cause/effect of having a player registered in a team. When scorecards are entered manually into MyCricket rather than livescored, and catches/stumpings are recorded only in the fielding section at the bottom of the the MyCricket scorecard and not in the actual scoresheet, I have to go in and add the player to the team manually, before I can add them as a fielder in the scorecard so as Cricketstatz recognise the catch/stumping. This is even though this same player has batted/bowled in the match. Not holding up a lot of hope for a change, but is a pain to have to go into multiple screens with players going up and down between grades. Please let me know if you would like me to add it to "suggestions".
Thanks for posting this one up. It is a good discussion point.
You are indeed doing it correctly.
I just want to mention that you probably don't have to do it for ALL matches where there is a retirement. We previously (prior to the introduction of the Retired At/Returned At system) had a system where you could double-up on FOW entries so that retirement partnerships would calculated correctly - so if you have any of these then you can just leave them if you like.
Also, there will be plenty of retirements where they retired at a very low score - so these would have minimal impact on partnership records, especially where the surrounding batters had low scores as well.
That being said, I see the pain of having to go out and change the team temporarily so that you can update the old match retirement info.
A possible solution - I like your idea of limiting the retirement player selection to only the batsman that are listed in the batting section above. This will require a bit of javascripting so I will look into it. It could also be done for the FOW player entries. It would have the added benefit of removing the chance that an unlisted batter be incorrectly selected.
I will post up a suggestion in the suggestion forum - be sure to pop over and like it/vote for it.
Hi Paul, the method you are using is the only way I have found to do such tasks.