Resolve data import conflicts

Hinweis: Data conflicts are not detected in trial balances. Where an existing trial balance contains data rows with the same Account Number values as a newly imported trial balance, the new trial balance data overwrites the existing trial balance data rows.

For every row of data you import into Caseware Cloud, a unique identifier is created automatically using the values of one or more fields present in the data row. Where the data source is either a CSV or Excel file, data conflicts may be detected after you assign fields from incoming data to Caseware fields. See the scenarios below and how to resolve data conflicts in each. For more information on importing general ledger data from CSV or Excel files, see Import the client’s transactions from a CSV.

See Understand subledger datasets for more information on how unique identifiers are formed in subledger datasets.

See Understand the General ledger dataset for more information on how unique identifiers are formed in the General ledger dataset.

Data conflict in the same CSV or Excel file

Data conflicts occur within a CSV or Excel file if more than one data row has the same unique identifier:

• A warning icon and a Reassign button appear in the Uploaded files section on the Import Data window.
• If you hover over the warning icon, the following message appears, “Resolve conflicts in the data source before you reimport.”

To resolve data conflicts in the same import file:

1. You have these options:
   1. Delete the file from the Uploaded files section by clicking ( ).
   2. Make sure that you are assigning the correct column to the Caseware field used as the primary key by clicking Reassign. See Quick reference to conflicts by data type, which lists the fields used to form the unique identifier by default in each dataset type.
2. Open the file and delete or modify any duplicate data rows. Below is a quick reference to the fields whose values can cause data conflicts if they are the same in two or more data rows.

3. Reimport the fixed file.

Data conflict between the dataset being imported and an existing dataset

If there is already a row in the dataset that has the same unique identifier as a row you are trying to import, a data conflict arises. Quick reference to conflicts by dataset type lists the fields that cause data conflicts if their values are the same in the file you are importing and in the existing dataset. In addition, data conflicts only ever arise in the same dataset type. For example, there will never be any data conflicts found between a newly imported general ledger dataset and an existing subledger dataset.

In this scenario, a warning icon and a Resolve conflicts button appear in the Uploaded files section on the Import Data window.

To resolve a data import conflict between the incoming file and an existing dataset:

1. On the Import Data window, in the Uploaded files section, you can either delete the data source you just imported by clicking ( ) and import a different file, or click Resolve conflicts to use one of the data conflict resolution options. If you click Resolve conflicts, continue to the next step.
2. You have these options:
   1. Resolve conflicts using data from <data import file name>
      1. Select this option to overwrite the data rows in the existing dataset with the data rows whose identifiers are the same in the newly imported data file. Click Next.
      2. You are prompted to confirm. Click Continue.
   2. Resolve conflicts using data from <name of the existing dataset>
      1. Select this option to disregard the data rows in the newly imported data file whose identifiers are the same as those in the existing dataset. All other data rows whose identifiers do not conflict with the existing dataset are imported. Click Next.
      2. You are prompted to confirm. Click Continue.
   3. Download CSV file of conflicts

   Click this link to download a CSV file of the data rows where conflicts have occurred. Analyze the file and then proceed with one of these options:

   1. If you determine you want to use the data in the existing dataset, select Resolve conflicts using data from <name of the existing dataset>. Data rows with conflicts in the import file are not imported. All other data in the import file is imported.
   2. If you determine you want to use the data in the import file, keep the data import file as it is and select the Resolve conflicts using data from <data import file name> option. All data in the import file is imported. Data rows in the existing dataset containing conflicts are overwritten.

   3. Delete the data source you just imported, fix the import file by removing the data rows with unique identifiers that are the same as in the existing dataset and reimport the file.

Resolve data conflicts using data from a newly imported file

When you choose to resolve data import conflicts using data from a newly imported file, and then later delete that file, the conflicting data rows are removed from the dataset completely.

The following case can happen depending on the degree of overlap between the newly imported file that was deleted and existing data rows in the dataset.

Newly imported file is a superset of a previously imported data file

In this case, a data file is imported into a dataset.

A second file including all the same data rows in the first file as well as some new data is imported into the same dataset. A data conflict is detected because some data rows in the dataset and in the incoming second import file have the same unique identifiers.

The user opts to click Resolve conflicts, and then selects the Resolve conflicts using data from <data import file name> option.

The data from the newly imported file overwrites the previously imported file. The resulting dataset now only contains the data in the newly imported file.

However, the newly imported file, GeneralLedger_ImportFile2_Superset.csv in this example, which was used to overwrite the first imported file is deleted.

This results in an empty dataset. On the Datasets page, notice only the first file that was imported is listed, which in this example is GeneralLedger_ImportFile1.csv. If you export the dataset, you are prompted with a warning.

How you resolve the empty dataset depends on what you want to achieve:

You want the dataset to contain the data from the second, larger import file you imported last

• In the Source column, delete the file you imported first, which in this example is GeneralLedger_ImportFile1.csv.
• Reimport the second data file into the dataset, which in this example is GeneralLedger_ImportFile2_Superset.csv.

You want the dataset to contain only the data from the first import file

• In the Source column, delete the file you imported first, which in this example is GeneralLedger_ImportFile1.csv.
• Reimport the first data file into the dataset.

Quick reference to data conflicts by dataset type *

Dataset type	Conflicts occur where this field has the same value in two or more data rows
General ledger	Entry ID (entry_id) - Line Number (line_number)
Accounts payable—invoices	Transaction ID (ap_invoice_transaction_id)
Accounts payable—payments made	Transaction ID (ap_payment_made_transaction_id)
Accounts payable—suppliers	Supplier ID (ap_supplier_supplier_account_id)
Accounts payable—open balances	Transaction ID (ap_open_balance_transaction_id)
Accounts payable—invoices	Transaction ID (ap_invoice_transaction_id)
Accounts receivable—cash received	Transaction ID (ar_cash_received_transaction_id)
Accounts receivable—customers	Customer Account ID (ar_customer_customer_account_id)
Accounts receivable—open balance	Transaction ID (ar_open_balance_transaction_id)
Inventory transactions	Transaction ID (inventory_transaction_transaction_id)
Inventory on hand	Transaction ID (inventory_on_hand_transaction_id)

---

* In the Quick reference to data conflicts by dataset type table, it is assumed you have assigned a field in the import file to the Caseware field indicated. By default this field is the primary key for the dataset and its value is used to autogenerate the unique identifier for each data row. Where you do not assign a field to the field designated as the primary key for the dataset, other fields designated as alternate primary keys are used to autogenerate a unique identifier. See field descriptions for the dataset type in question for more information: Understand the general ledger dataset or Understand subledger datasets.