Quote:
|
Originally Posted by jdettbarn
A little update on my error:
Checked the Fielding table... Found a bunch of current season players with 0 for the year. Deleted them and re-imported. All teams/players imported into this table seemingly correctly.
Then checked TeamPost Chart after making the above change. All teams are there now. Everything looks (seemingly) OK.
Also checked the FldStarters table... here is where the weirdness happens. All teams in the FL (team ids 1-8) were imported correctly. The rest of the teams (9-16) did not import for 2018. Team ID 9 is ATL, which just happens to be where the HTML generation sticks during the Team Positional Charts. So it seems like something happened with ATL during the fielding import.
And I still get the same error during HTML generation... Now I'm not sure why the Team Positional Charts don't generate now that the table is finally (seemingly) correct. But the whole FldStarters thing has me confused too.
Any ideas would be greatly appreciated... for now, I guess I'll be checking out the fielding CSVs, specifically ATL.
|
Atlanta was the first team in the other league processed so my guess would be that once the 0 year records are deleted from the table and all tables that have 0 year records it should process from the csvs all right. Just make sure that you don't re-run the import with the exporter option on.. Turn this off and copy the csvs from the 2018 folder into the data folder. Then from the menu delete the 2018 season and rerun the import with the exporter option off..... if this fails again then do the same process but look at the csv files within excel. Look specifically at the Atlanta records first...
Hope this helps...