Bulk Import doesn’t like commas in fields

[parks]

Just an FYI in case you are not aware of this. I found the bulk import was not importing “random” records even though the message after the import said that all records had been imported successfully. It took me a while to figure out that I had some address fields that included a comma (e.g., 123 Main St., Apt #100). Any record with a comma in the address did not import into the database.

Once I figured this out, I removed the commas and the records imported just fine. This “feature” drove me nuts for some time before I discovered what was happening.

It would be helpful if the software either accepted the commas, or produced an error message for records with commas. If I didn’t double check the count of records imported vs. what I expected, I would have never noticed that some records did not import. The import message left me to believe that it worked fine.

Other than this, the import works great!

Regards,
Terri

[wzp]

It would be helpful if the software either accepted the commas, or produced an error message for records with commas. If I didn’t double check the count of records imported vs. what I expected, I would have never noticed that some records did not import.

CSV = Comma Separated Values. We have no control over the limitations inherent to the CSV standard.

• This reply was modified 1 year, 10 months ago by wzp.
• This reply was modified 1 year, 10 months ago by wzp.

[Author]

Posts