I am importing a simple Excel sheet into Adagio Invoices. I get error message, "Could not import variant of type (error . . .)" All data types in the import template seem to correspond with the data. Anyone ever seen this?

Hi Brian:
Try exporting a batch with the same fields selected and compare the 2 files. Then try importing the newly exported batch. If it imports, the problem is with the original file. If it has the same error, the problem is deeper. I'd suspect the former explanation.

Hi Brian,

That message indicates that you are trying to use Excel to import a file that has a format of Header / Detail / Detail (ie a header line on one row, followed by the first detail on a different row.

Excel doesn't support that format (the header fields must be repeated for every row). And I don't believe that Adagio Invoices supports the above Header / Detail / Detail format anyway (like OrderEntry does).

Bruce's comment is right on - to see the expected format, export a batch. Also check out the Help file and the very detailed notes about setting up Import Invoices templates - from the main Help menu, choose Importing Invoices or Items, and near the bottom of that page choose the link to 'Import Invoices - File Format Requirements'. Or the link on our website for Import Tech Tips.

This is a file that I have been importing to AI successfully for several years. It only failed after I upgraded to AI 9.0B. As suggested, I did a sample export and saw the problem right away. The first field that AI 9.0B exported was IN, indicating the Header Type. My import file has I in the Header Type field, a change that I had failed to notice. I assume that it will work after this change. I will be at the client's office tomorrow and will test.

Thanks.

Every row on my import file begins with I. My file is definitely not the layout you mention.

So Brian, is it working OK now?

Yes, it is working. Don't try exporting and re-importing to verify formats because the exported header type is IN and the required import header type is I. The real problem however, was a string that had somehow crept into a numeric field. It is a very large file and I overlooked this when checking it visually. The error was deep in the file, yet the import stopped at the outset.

All's well that ends well. The client is smiling once again.