Hi Vince,

Can you re-post which fields are selected for your import template? The easiest way to determine this is to open the import template and print it using the Print button at the right. This is a hard question to answer without knowing precisely which fields are associated with the format you included in your post.

Make sure that you have only 12 fields selected in your import template (8 Header and 4 Detail) because that is how your import file is defined.

I copied your format, made some assumptions as to what the fields were, and changed some values to match the Adagio Receivables sample data. After including the other 'required' fields as defaults on the 3rd screen of the Import function, I was able to import the invoices with no errors.

My guess is that the import template you are currently using is not quite correct. Are you using the most current release of Adagio Receivables (020610)? After choosing the desired 12 fields, go to the Defaults screen and clear everything. Try to import the file, and you will probably get a message that a specific field is required. Select that field from the list and set it as a default value, and save the template. This process will have to be repeated a few times until all Required fields have been included as Default values. At this point, I would anticipate that the import will work correctly - it did for me. Your import file is likely correct and the Template is what requires adjusting.

Regards,

Hi Vince,

Well those fields were the same ones I tried with sample data, so the problem isn't with field selection. There shouldn't be a maximum number of records for importing. I have imported batches with a thousand records and not receive errors.

The reason for a 'Corrupt data - invalid field' usually has to do with an extra or missing comma, throwing the field count off. When you get an error, it will indicate the record and field that the import process is complaining about. If you open the import file with a Text Editor (not Excel), find that record number. Probably in the line or two above it, there is a missing or extra comma. Also make sure that there are no commas at the end of a line (there aren't in what you posted earlier today).

Also make sure that you don't have any strings that exceed the maximum length. I have seen one situation where someone tried importing invoices using a 13 character invoice number field. If the batch was only a few invoices, it completed sucessfully. If there were quite a number of invoices, then an error was reported and importing halted. Though what you posted show 12 character invoice numbers, make sure that this and other fields do not exceed the maximum (as indicated on Template printout).

Lastly, make sure that you don't have any extra quotes " or double quotes such as ,"" "", as there have been reported issues.

If you get an error with the 7-record file you indicated earlier, can you re-post the exact error message you get, including the record number and field name? If what you posted was just a sample of the import file, please reply with the exact error message just the same.

*** I couldn't find your company record in our database, and I don't know who your Adagio consultant is. If you can let them know you are having a problem, perhaps we can work through your consultant to find out the problem.

Regards,

Hi

I have never heard of this being the cause for the types of messages you are getting during the import process. I suppose it cannot be ruled out completely - however, I would be quite surprised if this was the cause.

I will say that in most import issues, the errors returned are quite generic, even cryptic at times, and in some cases do not necessarily point to the actual problem.

Do you have another computer or workstation on your network that is setup for using Adagio Receivables where you could compare the import process?

Have you taken a look at the sample data (Softrak\CRWIN\Samdata) and the sample import files there (ARCASH, ARCREDIT, ARDEBIT, ARINV, ARINVJC)? They are all .csv files that you can look at and compare to yours.

Alternatively, your Dealer could contact us and if possible, we could get a copy of one or more of the 'problem' import files along with a zip of your data (so it would match the file)...? We could then assist in trying to get this resolved asap.

Regards,

Forgot one more thing that could be very important. Is the file 'type' you are trying to import a .csv (ASCII CSV (Delimited)) or a .txt file?

Looking at the way your fields are laid out - you should be using the (ASCII CSV (Delimited)) format. You do this at the 1st 'File Information' tab in the Receivables Import screen, under the 'File type' scroll box. The .csv file type does not rely on exact field width, but on the commas to separate fields.

Text format .txt is 'fixed width'. If using this format, your import file fields must account for every character expected for that type of field. It is far more finicky than using the ASCII CSV format.

Regards

Vince:

After correcting the problems with your import file layout I was able to repeatedly import it without any problems. Specific problems that must be corrected:

Error at record 45. Error did not always occur at the same place. Error not specified:

Correcting the Terms Code from " C.O.D." to "C.O.D." corrected this problem.

Error at record 364 (row 727) invalid customer number. Add missing customer number.
Error at record 452 invalid customer number. Add missing customer number.
After this I correct all missing customer numbers without noting the specific record number.

You must correct your process so that the issues noted above do not reoccur. If you send me a fresh output I can confirm that it is correct (or not as the case may be).

Please note that the Customer number and Terms code are validated fields and must be absolutely correct for all records. For the terms code issue I must assume that the extra space causes confusion rather than an out right rejection of any particular record.

The NULL Due date and Discount Date in the template do not appear to cause any problems but I would not want to guarantee this. It may be safer in the long run to include these fields in the import file (by populating them with the invoice date) rather than relying on including them in the templates.

To clarify Doug's point about the Terms code, the extra space can cause 'confusion'. It makes the field 7 characters long, when the maximum length of that field is 6. Perhaps we should be giving a more appropriate warning, but the end result is that for larger import files there will likely be some sort of error. I have seen this behaviour before - see our second posting and the '13-character' invoice number field.

Though we have not seen any problems with having the Due/Discount date field as 'Default' values, Doug's point about including them anyway in the import file is also well taken.

Regards,

Vince:

Please email me a copy of your current import file and I will have a look at it.

I doubt that your current problem is a result of the due date issue.