Hi,

Please have a look at the following article in our Knowledge Base:

210-30223 - "CSVI.C Open-ended quoted string" Error Occurs When Importing

Solution or Workaround

The error is most likely caused by an invalid character entered in the source company. The invalid character will cause the entry to breakup into two separate lines in the import file, causing the first line to end without a quote.

To resolve the problem:

Remove the invalid character from the entry in the source company and re export the records.

Correct the import file by deleting the carriage return, and combine the two lines back into one

Note: Provided in the KB article is a link for a utility that automates the process of removing the carriage returns. Note, that this utility cannot account for all scenarios and therefore may not remove the carriage returns in some cases. If the utility does not remove the carriage returns, then you will need to manually remove it.

This is caused by embedded double quotes, like an transaction entry description of:

This is a "perfect" excuse

Just edit the file in notepad and take them out, or make it:

This is a 'perfect' excuse

I know this is an older thread and appreciate it as it helped me with quickly determining why this happens and how to fix it.  But instead of a KB article and command prompt exe, wouldn't the better solution be to update the GL Consolidation export process to address this given that its a known issue?

Hi Kevin

Yes you are right I also think if Consolidation Export program could able to detect and correct this kind of strings while generating export file then it can be avoided without workaround.

Another way is to create macro which do same as above work around program and triggers when export is processed.

Regards,

Pratik

The other thing you should be doing is finding what the error is, usually a comma in a description field in the source data and making sure people don't enter it in the source companies then you don't have the problem when importing