Error in importing files

himanshu

Hi Support,

i got a problem after updating to latest build (1204), while importing csv files it gives following error:

-Error reading input file. Importing data has been terminated.

com.bas.basserver.executionengine.ExecutionException: Import file is corrupt or does not have description of colums.
	at com.bas.basserver.executionengine.a.execute(Unknown Source)
	at com.bas.basserver.executionengine.o.execute(Unknown Source)
	at com.bas.basserver.executionengine.ExecutionEngine.a(Unknown Source)
	at com.bas.basserver.executionengine.ExecutionEngine.startChildProcess(Unknown Source)
	at com.bas.basserver.executionengine.ExecutionEngine.importData(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.bas.basserver.executionengine.a.k.a(Unknown Source)

at com.bas.basserver.executionengine.a.k.a(Unknown Source)

at com.bas.basserver.executionengine.a.d.if(Unknown Source)

at com.bas.basserver.executionengine.a.d.char(Unknown Source)

at com.bas.basserver.executionengine.a.d.int(Unknown Source)

at com.bas.basserver.executionengine.a.f.a(Unknown Source)

at com.bas.basserver.executionengine.a.f.if(Unknown Source)

at com.bas.basserver.executionengine.a.f.resume(Unknown Source)

at com.bas.basserver.executionengine.ExecutionEngine.a(Unknown Source)

at com.bas.basserver.executionengine.ExecutionEngine.handleServiceReplyNotification(Unknown Source)

at com.bas.basserver.bsmanager.f.a(Unknown Source)

at com.bas.basserver.bsmanager.f.a(Unknown Source)

at com.bas.basserver.iopipes.ComponentSink.processMessage(Unknown Source)

at org.openadaptor.adaptor.STPipelineController.processMessage(Unknown Source)

at com.bas.openadaptor.NonTransactionalController.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimplePipe.processMessage(Unknown Source)

at org.openadaptor.adaptor.STPipelineController.processMessage(Unknown Source)
at com.bas.openadaptor.NonTransactionalController.processMessage(Unknown Source)
at org.openadaptor.adaptor.AbstractSimpleSource.processMessage(Unknown Source)
at org.openadaptor.adaptor.AbstractSimpleSource.sourceProcess(Unknown Source)
at org.openadaptor.adaptor.AbstractSimpleSource.sourceProcess(Unknown Source)
at com.bas.openadaptor.a$a.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

while investigating i found that there is some change csv format, before all fields are comes in separate columns but now all fields are in one columns with comma separated.

please take on priority ..thanks

aware_support

There were no changes in the format of the CSV file. Try exporting something and importing it back - will it work?

Then look at the format of the file that export creates and check if your import file conforms to this format.

bazar2009

I agree with himanshu that there are differences.

In previous versions when a file was exported when the .csv was opened in Excel it would automatically separate the data into separate columns. The latest version (1204) has all of the data in column A and displays the comma separators.

This is different than how it used to work. I have done a lot of work providing templates so that people can import the data (based on the previous export formats). They do not work now.

This is a problem

himanshu

Hi Support Team,

i checked by exporting the business object and found that previously all attributes are coming in separate columns which is not now.

Now all the fields are coming in one cell of column separated by comma.

as you can see in the error code also it is saying something related to column.

bazar2009

Also, support please note that any changes made in excel cannot be done in a column. I can only modify the new exports in a text editor and then re-import. This is really a step down for me. There has to be a way to edit the import files in a columnar fashion without major workaround hoops to jump through.

tford

This is a major issue for me as well.

I am sending a sample bsv to support.

From the build 1204 list of changes:

"Unicode" encoding is used rather than UTF-8 in CSV file export/import for comaptibility with Excel

I'm guessing this was the cause of the change.

aware_support

We'll have a look and issue a patch ASAP. Apologies for the inconvenience.

aware_support

This has been fixed in build 1205

himanshu

Thanks Support,

For the quick response.

😃

bazar2009

Fantastic!

Thank you Support

Libero

Was playing with trial version of the build 1399, the exported csv shows again all headers separated by comma instead of column...seems the same problem is back again.

Libero

And here below the error if I try to import a csv :

"
Invalid description of data column G.CID; G.TransactionNo;G.Product. It must not have more than 2 dots"

aware_support

Have you read the error message? You have an incorrect header line in your BSV. Please double check it. For a start, values are separated by semi-colon, rather than comma.

Libero

The error message shows semi-colon but my csv header is not separated by semi-colons. All attributes are in separate columns as usual. I made a test using a csv with one atttibute " BO.Dummy", the import works. If I use " BO.Dummy, BO.Dummy2 " I have the same error.
Before build 1399 I use to import csv using headers in columns, not the one cell of columns separated by comma.

Thanks

Libero

Fixed now, the original xls has created hidden columns within a column during the export to csv. Seems an Excel bug, import works fine now in build 1399 and Beta 5.
Thanks

Sergej

After imorting csv that contains lines in russian text now in system they are displayed as ??? signs. But if I enter manually russian text displays correct.

Is import feature in UTF-8?

aware_support

Import feature definitely supports UTF-8. Check that your operating system does.

Sergej

I have tested it in debian and win7. imported russian lines are in "?" signs.

Sergej

Also I have tested it on third machine with Windows XP and the same result. I import it in testing mode.

Sergej

If someone has problem with import csv containing non-english words and encoding of csv of excel, the solution to me was to create csv in google docs and then save it to desktop and import. My MS Office had encoding problems with csv.