Hi Aaron - we are importing from Scoutbook and are encountering where the date appears to be formatted correctly in the CSV file, but the import shows the dates as “0025/01/01” We don’t know why it is dropping to lead “20” and this is resulting in some duplicates being imported. Any ideas on why that might be happening?
@KristineDeLisle,
I agree that for SB+ directly entered data ie from summer camp or outside/online MB counselors etc it would be great to import into TT. I am hopeful that as SB+ gets more mature it will allow for more targeted (ie, individual scout) exports of such data that can then be setup to import into TT easily. That does not exist as of right now.
I really don’t use the import functions for my own Unit, because we use TT as the main system of record. We are small enough that Summer camp and Outside MB’s are just entered manually into TT rather than imported from SB+. I did some testing with some manual data to test what Wade was seeing but was not importing the entire data set from SB. I did not see any date issues on import, I even formatted the date different ways and it always imported properly into TT.
Are you opening the SB export CSV and making any changes to it before importing into TT?
It’s possible. We have a scout where there is an ID issue which when they are included, causes the import to fail. In the past, I successfully imported “edited” records - I had removed old entries but that was only deleting rows, not editing columns. That seemed to work fine.
Sometimes, depending on the editor you are using it can introduce other formatting into the file. If you are importing into Excel making edits and then exporting a CSV that should be fine just look at the exported CSV with a text editor to make sure it did not make some change to the date formatting or something like that. That would be the only thing I could think would cause a problem like this.