.CSV Import Errors and Common Fixes

Owned by Benjamin Hacker
Last updated: May 16, 2023
5 min read

Table of Contents

Overview

  • This is a list of common import errors that users may see when importing .csv documents into CMA and the steps to take in order to correct the document or mapping of the data. This list will continue to grow as we identify more user generated errors.

Required Permissions

  • Various permissions depending on the import tool being used. Add/Edit/Delete for Journal Entries, Budgets, Inventory, Invoices Etc..

.CSV Template Mapping Error

 

Problem: When users receive the above error within the mapping section of the import wizard, CMA is letting us know that something on the .csv is not correct. In this example the user was importing a budget and CMA flagged the words “Pro Shop” and ledger “Uniforms” on a specific row in the .csv.

Solution: Close the Import wizard and then correct the data on the .csv and be sure to save. Once the changes are done, attempt to import the .csv again using the import tool.

.CSV Naming Convention

 

Problem: The above error, historically, points towards an issue in the naming convention of the .csv being used. In this example, the error was thrown because the name of the .csv had periods (.) in it.

Solution: Rename the .csv file and then attempt your import again. This error should cease.

Data Mapping

 

Problem: The Account and Department columns in the spread sheet do not match the exact account numbers and department numbers in CMA, as the Account_Lookup and Dept_Lookup are not pulling in anything automatically.

Solution: Select the account line then select lookup to the right, a pop-up window will appear and you will then be able to link what is on the .csv to the actual account in CMA, do the same thing for the departments. Please see the Budgets video to see this in action. Alternatively, you may edit the original .csv so that the department and account numbers match exactly as they do in CMA.

.CSV Open Error

Problem: User is trying to import a .csv and the above error populates preventing them from importing their .csv.

Solution: This error populates when the user has the .csv they are trying to import open on their desktop. Close the error, close out of the .csv document and then attempt to import the .csv. This error should no longer populate.

Data Formatting

 

Problem: In the above image, the user was attempting to import a journal entry. The error is telling us that CMA cannot convert $170.00 to type Decimal.

Solution: When importing a budget, journal entry or any other entry that contains currency values, you should code the .csv to be a number with 2 decimal places as CMA will not read the dollar symbol ($). Access the .csv and convert the currency cells to just be numerical cells with 2 decimal places. Save your .csv and then attempt to import the document again. The error should no longer populate.

Out of Memory

 

Problem: This client was attempting to upload a large .csv document. the System out of Memory error was thrown.

Solution: When a user gets this error the .csv file is too large and will need to be broken in to two different files. This example had an extremely high number of rows, this is not a common error.

Column Definitions

The image above is one commonly seen when importing Budgets, Journal Entries, Invoices and Member Charges. Each name on the left will represent a column on the .csv. The type on the right needs to be mapped according to the data that exists below it’s column. Below you will find definitions of the types of data that can be used:

  1. Account - Refers to Account number being used

  2. DateTime - If the import requires an actual Date or Time, this type will be used. This is not commonly used as the year field for budgets is to be coded as an integer.

  3. Decimal - This is used when you are importing dollar amounts or fractional qty.

  4. DepartmentName - Not used anymore but was used for imports that had department name.

  5. DepartmentNumber - Used when linking department numbers from a .csv

  6. Integer - Used for all other numerical based fields on an import. Whole qty lines for invoices and budget years need to be marked as Integer.

  7. String - This is used for Description and Reference fields in reports that use them and Item Name fields for Member Charges or AP Invoices. Text data should be mapped as String.

  8. YesNo - This field is typically used for importing Member Charges and corresponds to the section for Service Charge and Tax exempt within the Member Charge Wizard. On your .csv these columns should have a yes or no and should be mapped as such within the import wizard using a Y or N.

Best Practices

FAQs