Dear Forum,

I am implementing a client that uses a customized solution to generate invoices but I need to update the core accounting modules AR and IC so I bought the INVOICE MODULE 8.1B to pull the data into the accounting cycle.

The (Import/Export)feature does not seem to be the same as for the other modules.

Problems noticed:
1: Error "File path exceeds 65 characters and has been truncated".

2: When I get an import error on the batch I am doing a batch number is still created with either zero entries or only those items which were read successfully.

3: Import Batch Description now only reads Import Batch the name should reflect the name of the file imported so an audit trail can be established.

4: There is no validation being done on the import file to say what are the possible errors which needs to be corrected.

5: I started out trying to create an excel spread sheet but had to abandon and revert to a CSV Delimited file. The same file just saved as a CSV imports fine. There needs to be a review of this too.

6: After importing the file and posting in the invoice module, I now notice that the information for the customers in the AR Module is not showing a DOC Date and a DUE Date but they were present in my Invoice Module Batch when I checked it before posting. This I need an urgent response ..Thanks .

Hi chinmook,

1) Put the import file in a directory with a shorter path. There is a maximum 65 character path+file name limit in all Adagio programs for importing.

2) A 'verify before import' feature is currently not available in Invoices 8.1B as is for other Adagio programs, but it will be there in the next version.

3) All Adagio import batch functions do not put the file name into the batch description - typically the file name will always be the same. I can forward these feature suggestion to the programmers.

4) Verify before import is coming.

5) Adagio Invoices supports both Excel and CSV formats, but does not support importing XLSX (Excel 2007) files. Try saving as an Excel 2003 document.

6) We aren't aware of any problems with the document and due dates not posting correctly to the AR transactions, especially if they imported correctly. Can you replicate the error? After import, can you verify that the document date and due date are as they should be?

Thanks...its actually xls file but I have solved same by simply deleting the header row and saving as a CSV file and it imports sweet.

Hope the new version roll out will be soon.