GL Consolidation Error - Delimiter/Other Characters

[iwells]

Hi,

I'm panning through several ongoing issues and have come across one that someone else must have run into. When doing our GL consolidation export (v5.5) we encounter errors from the data during the import (v5.6) that cause the import to stop. The errors are caused by delimiter characters (commas, quotes, etc) in the gl description/reference.

I've checked the product updates for 5.6 and 6.0 (I couldn't find anything on ERP 2012), but was unable to find any mention of a fix. Is there a fix or is this and outstanding issue?

 

[ettienne]

You can't export from 5.5 and import into 5.6

 

[iwells]

Hmm ... not to be argumentative, but we are currently doing this with multiple branches where we export from v5.5 and import into v5.6. Can you be more specific and provide a reason why you can't do this?

Then back to my question, since the import is in v5.6 have you ever encountered this? That shouldn't matter since the export and import are independent unless there's a fix for the v5.6 gl consolidation export.

 

[ettienne]

I designed the program.
Expecting an export from one version to import into a newer version is a fool's folly IMHO.
The GL transactions export files are created in the typical GL import file Single CSV layout. So you can open a GL batch and click File, Import and point it to the transaction file and import it - then see what error messages reported.
As for commas or quotes causing an issue, I don't know about that. You can enter both in a GL batch, export the batch and then import it as a test - no errors generated. GL Cons uses the exact same export/import engine so there should be no problems there.

 

[iwells]

The exact error is "CSVI.C - Open-Ended Quoted String" and I can open the file make the corrections by removing the commas from the text fields in the file and it works fine. Additionally I can confirm the records all end correctly and there are no line breaks.

I don't disagree this is not the preferred method to export and import between versions, but theoretically speaking, if the export/import format and fields have not changed across versions then there's no risk in doing so. Exports and imports between GLs are straightforward from an accounting perspective and that logic is never going to change so there shouldn't ever be logic changes in processing the data, only formats changes of the data. Transactions out to transactions in in JE form.

 

[ettienne]

Import formats are notorious to change with each version, if an import format happens to be the same then it is pure luck.
Contact Sage tech support and see if they have any answers.

 

[ettienne]

CSVI.C - Open-Ended Quoted String" has been reported on several old versions, it relates to having quotes in the GL data fields.

 

[johnhugh]

I'm having the same issues in Accpac 6.
I can run a GL consolidation export but get the "CSVI.C - Open-Ended Quoted String" error when trying to import it.
I have to then use Notepad++ and remove additional line breaks that must have been added due to quotes being used in the GL transaction description or reference.

Would really like to see a fix for this.

 

[iwells]

Yea we still get this periodically ... depending on line breaks and other random characters in the data the file fails. At least we know what we're looking for though it's a pain when you consider how many lines you can be scanning and how little effort it would take to scrub the data.

 

[johnhugh]

Can you think of a way to do the clean up with a batch file or similiar?
For example, look for lines that do not end with a quote, go to the last character in that line and remove the carriage return and line feed.

Would that work?

 

[ettienne]

How about contacting Sage Accpac tech support and logging an issue? If this issue is not brought to their attention then it will never get fixed.

 

[iwells]

John: if I had more time I'd do exactly what you're describing ... I have bigger issues at the moment.

Ettienne: I think it is logged on the community site according to old posts I read.

 

[ettienne]

That does not mean it is logged with tech support- they do not monitor those sites and fix errors.

 

[johnhugh]

Where do I have to log it?
Is there a website?

 

[ettienne]

In the USA call 800-253-1372, otherwise call your local Sage support.

http://na.sage.com/sage-300-erp/product-support

 

[johnhugh]

I've worked around this now by using search/replace in Geany and regular expessions.

http://www.geany.org/

search: ([^"\r\n])(\r\n|\r|\n)+
replace: \1

That will fix all incorrect line breaks. Only issue that remains in our case is if the GL description for example ends with " (inch)