Phantom Entries in TS import csv file

We have been using TS import with TS 20011 both with time and expense templates without.  Since converting to TS 2017, some csv files contain "phantom" entries which cannot be seen when the CSV file is opened.  The only thing that stands out is when I scroll through using the TS import window, I can see blank entries there.

  • 0
    Sounds like some rows in your file that you are not seeing. Try opening the file in excel. Then copy the rows and columns you need and paste on a brand new workbook. Saw the new workbook. Then try the import from the new workbook.
    Alternatively you can try going to the last real roe of your file and then highlight a range of rows and delete. Less time but less accurate the second way.
  • 0
    What does the TSImport Journal say about them? Does the import fail on them? It should tell you which row it thinks it is and you can then look at your source file to try and figure out what that is.
  • 0 in reply to Nancy Duhon
    The journal says the only failure is the first row which is the header. I suspect this is another TS 2017 problem. I thought the journal was suppose to pick up errors but it is not picking up all of them.
  • 0 in reply to adonders
    Hmm. Okay, what makes you think you have "phantom" entries then? I'm not clear on what the problem is we are trying to solve. What about them is "phantom?"
  • 0 in reply to Nancy Duhon
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    ,,,,,,,,,,,,,,,,,,
    This is hidden in the CSV but appears in notepad. While we can just delete it prior to import, this would add a layer that was not there in TS 2011. In 2011, it would simply skip these incomplete entries and show in the journal. Timeslips has identified this as another "broken" piece in 2017 and sent it back to development. We have decided to revert back to 2011 until Timeslips fixes these problems which are critical to our billing. Thank you for your help.
  • 0 in reply to adonders
    If Notepad shows them, they are definitely in your source file.

    It sounds like in v2011 your import just failed to import the records, which was fine with you, and along you went.

    But you still have not explained what alternative behavior you get in v2017, only that it is "broken." Does it stop and prompt you or something?
  • 0 in reply to Nancy Duhon
    I had a similar situation and the problem was that the "save as csv" from Excel included extra rows which was what caused the problem.
  • 0 in reply to Terryr
    8005894126-phantom entries during TSimport. This a known issue and has been assigned a trouble ticket. Does anyone know when this fix will be implemented?