Has anyone had the CSV importer just basically ign...
# general
r
Has anyone had the CSV importer just basically ignore stuff in a source file? I ran an update import to correct a non-GL impacting field totaling ~9000 lines on ~4700 invoices. CSV run completed and said 4700 of 4700 successful, but there are lines it didn't change. I caught it only because I was monitoring a search that would have records drop off of it once the CSV run was completed. I was confused when the CSV run completed, but there were still records on my search. 1. I triple-checked that the info that didn't update was in the source file 2. I intentionally didn't use multi-threading since in some cases, I was setting it to update multiple lines on the same invoice 3. It did not (that I could find) update some lines of an invoice and not others, which is what I would have expected if it was getting confused by the multiple lines on the same invoice thing. It just completely skipped them 4. There are no running or relevant scripts or workflows running on the invoices 5. I checked the audit trail and it's not an instance of CSV importer updating the line and something else switching it immediately back. there are no line audit trail entries. I'm stumped. This is a little concerning because for the most part I trust the CSV Status screen to give me accurate info. Any ideas?
Nvm I figured it out. It was the Est Ext Cost field I was updating. The Cost Type was Item Defined instead of custom, so the updates were just getting ignored. Though I'm thoroughly confused why some lines had Cost Type set as Custom by default (the ones where the CSV update worked) and others had it set as Item Defined. All lines happened to be the same item, so I don't know why that wasn't consistent. Mildly annoying the system doesn't give you some warning of that.