After upgrading to Ledger V 9.0C when importing a CSV file of batch transaction details we get an invalid data error on a field that is defined as a string but contains a decimal number. The same file imported fine in v 9.0B and earier. As an example if we attempt to import a CSV file of batch, transactions, detail only, that has "97,200.00" in the Amount column of the ASCII file we get an invalid data message whether the import template specification for that Amount column is defined in Adagio as a string or a number.

Dave:
What happens if, as a test, you edit the CSV file and remove the comma in the number? See if the import process gets past that line before it stops again. Use Windows Notepad to edit the file.

I can confirm that having a comma in the amount will cause the import validation to fail. The solution is as Bruce suggested - to remove the comma within the amount string.
How is the import file being created? Can the process be modified to not write commas for the amount field?

We've run into this a couple of times. While you can remove the comma from the current file, if you are running this import regularly, and the import file is large, this might not be a practical solution.

In some situations, you cannot modify the number format directly in the program that is creating the file. If that's the case here, you can solve your problem by modifying Windows' number formatting.

From the Control Panel, select "Regional and Language options" (assuming Windows XP here). Then click on the "Customize" button.

Replace the comma in the "Digit Grouping symbol" box with a space.

You should now be able to regenerate the import file with the commas removed.

Note that this change will affect the number display in many different applications.