# Manage Multi-Case Tabular Data Import

Configure field mapping from case files to the target Vault object fields, allowing intake users to import a multi-case tabular CSV file and a multi-CSV ZIP file to _Inbox Items_, which can include up to 1,000 _Cases_. To set up your Vault to import data to targeted fields, you must [create the appropriate mappings][2] for each applicable health authority or partner. Your Vault includes [standard records][3] for Health Canada, which you can customize as needed and use instead of creating mappings.

For more information about multi-case tabular data import, see <a href="/en/gr/01135/#about-multi-case-tabular-data-import">Import an Inbox Item</a>.

## Prerequisite

Your Admin must <a href="/en/gr/01296/">enable Multi-Case Tabular Data Import</a>.

## Create Mappings

You must create mappings for each applicable health authority or partner to define how Vault imports multi-case data from that source. Veeva provides standard mappings for certain authorities, which you can use as a starting point by activating and then customizing as needed for your business process. For all other formats, you must create the applicable mappings, including a [_Tabular Data Format_][7] with the appropriate [_Tabular Source Files_][4], [_Import Field Mappings_][5], and [_Import Code Mappings_][6].

### Standard Mappings for Health Canada {#standard-mappings}

Veeva provides standard mappings for Health Canada. We recommend activating this standard record and updating it as needed, along with all related records. Alternatively, you can create new records. To use standard mappings:

1. Navigate to **Business Admin > Objects > Tabular Data Formats > Health Canada English (Standard)**.
2. Select **Edit**.
3. Update the **Status** to **Active**.
4. Select **Save**.

Review the [_Tabular Source Files_][4], [_Import Field Mappings_][5], and [_Import Code Mappings_][6] in the standard record and update them as needed for your business processes.

## Create & Update Tabular Data Formats {#tabular-data}

_Tabular Data Formats_ include the type of field mapping Vault uses to import multi-case data to Vault fields and the list of source files being imported. To create or update a _Tabular Data Format_:

1. Navigate to **Business Admin > Objects > Tabular Data Formats**.
2. Select **Create**.
3. Complete the following information:
    * **Format**: Enter a name for this record.
    * **Encoding**: Select an encoding type. If creating a format for VAERS, select **ISO-8859-1**.
    * **Country**: Select a country.
    * **Localization-based Mapping on Import**: Specify import mapping behavior. If you leave this field blank, Vault applies the <a href="/en/gr/740208/#domestic-cases">_Enable Localization-based Mapping on Import_ setting</a>.
      * **Import to Local Fields**: Vault determines localization based on the specified _Localization_ value of this record.
      * **Import to Global Fields**: Vault imports values based on derived values in the files.
   * **Localization**: If you selected _Import to Local Fields_ for the _Localization-based Mapping on Import_ field, select the applicable localization for imported files. If you leave this field blank, Vault imports to global fields based on derived values in the files.
4. Optional: Specify the default measurement values Vault populates on corresponding _Case_ fields when users import CSV files without unit values:
    * _Default Age Unit_
    * _Default Height Unit_
    * _Default Weight Unit_
    * _Default Report Type_
5. Select **Save**.

## Create & Update Tabular Source Files {#tabular-source}

Tabular Source Files specify the files being imported during multi-CSV ZIP import. You can create and update these files on a _Tabular Data Format_. To create or update a _Tabular Source File_:

1. Create and update records by doing either of the following:
   * Expand the section on the applicable _Tabular Data Format_.
   * Navigate to **Business Admin > Objects > Tabular Source Files** and select **Create** to create a new record or open an existing record to review and update.
2. Complete the following information:
   * **Name**: Enter a name for the source file, including the format extension. For example, `Assessment.txt`. The name cannot match the name of any other _Tabular Source Files_ in the _Tabular Data Format_. Ensure your entry is case-sensitive.
   * **Standard Format**: If importing **VAERS Symptoms**, select the option. Otherwise, leave this field blank.
   * **Target Object Name**: Enter the name of the object to which the source file is mapping. For example, `case_product__v`.
3. Select **Save**.

## Create & Update Import Field Mappings {#field-import}

_Import Field Mappings_ specify how imported tabular data maps to field and object records in Vault. To create or update an _Import Field Mapping_:

1. Expand the section on the applicable _Tabular Data Format_ and select **Create** to create a new record or open an existing record to review and update.
2. Complete the following information:
    * **Source Column Header**: Enter the name of the column header in the CSV file. Do not enter separators such as commas (`,`) or semicolons (`;`).
    * **Tabular Data Format**: Select the _Tabular Data Format_ this field mapping belongs to. If you created this _Import Field Mapping_ directly from a _Tabular Data Format_, Vault populates this field.
    * **Target Field Name**: Enter the field name of the Vault field. For example, `event_reported__v`. For _Date_, _DateTime_, and _Object_ type fields that have a corresponding _Text_ version, map the data to the _Text_ version of the field. For example, when mapping data to the _New Info Date_ field, enter `new_info_idate__v` as the **Target Field Name** instead of `new_info_date__v`.
    * **Target Object Name**: Enter the name of the object to which the target field belongs. For example, `case_adverse_event__v`.
3. Select **Save**.
4. Repeat these steps for as many column headers as needed.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault does not support certain fields, such as auto-calculated fields, which are ignored during data import and not processed. To see the list of unsupported fields, <a class="download-link " href="https://platform.veevavault.help/assets/downloads/saf-field-limits-restrictions.xls" target="_blank" rel="noopener">download this XLS file<i class="fa fa-download" aria-hidden="true"></i></a>.</p>
    </div>
  </div>
</div>



### ID Field Mappings

If your Vault contains pre-defined mapping already, you will see some source column headers mapping to the _Target Field Name_, `id`. For multi-case CSV import, Vault uses the `id` field mapping to reference a record in another row for a given source column header. For multi-CSV ZIP import, Vault uses the `id` field mapping to reference a record in another CSV file for a given source column header. For example, the following field mapping allows Vault to reference an _Adverse Event_ record on another _Case_ for a given _Case Assessment_ record:

| Source Column Header | Target Object Name | Target Field Name |
| -------------------- | ------------------ | ----------------- |
| Event ID             | `case_adverse_event__v` | `id`         |

For applicable source column headers, [create _Import Field Mappings_][1] to reference a record in another row (if multi-case CSV import) or file (if multi-CSV ZIP import).

## Create Import Code Mappings {#import-code}

_Import Code Mappings_ map source values to Vault-coded values for a given _Import Field Mapping_. Each _Import Code Mapping_ requires a _Code Mapping Type_, an expected _Source Value_, and a value Vault will map from your library. The _Code Mapping Type_ indicates which object type each mapping is based on, such as:

* _Controlled Vocabulary_
* _Device Code_
* _Dose Form_
* _Route of Administration_
* _Unit of Measurement_
* _Reason Omitted_
* _Seriousness_

Source values may be case-sensitive text or codes. For the Vault value, you must populate the field corresponding to the _Code Mapping Type_. For example, if you want to create an _Import Code Mapping_ for the value _Spontaneous_ within the _Report Type_ controlled vocabulary, you will:

* Select **Controlled Vocabulary** in the **Code Mapping Type** field.
* Enter any of the following in the **Source Value** field:
  * `1`
  * `SPT`
  * `Spontaneous`
* Select **Spontaneous** in the **Controlled Vocabulary** field.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If you create an <em>Import Code Mapping</em> with an <em>Import Field Mapping</em> for <em>New Info Date</em>, Vault uses this mapping to populate the field on generated <em>Inbox Items</em>, regardless of if a user populates the <em>Receipt Date</em> document field when <a href="/en/gr/01135/#create-inbox-item">creating <em>Inbox Items</em> from a multi-case file</a>.</p>
    </div>
  </div>
</div>



### How to Create Import Code Mappings

To create or update an _Import Code Mapping_:

1. Navigate to **Business Admin > Objects > Import Field Mappings**.
2. Select an **Import Field Mapping**.
3. In the _Code Mapping_ section, select **Create** to create a new record or open an existing record to review and update.
4. For **Code Mapping Type**, select an object type on which to base the field mapping.
5. For **Source Value**, enter the code or text value that would appear on source files.
6. Populate the field or fields that correspond to your _Code Mapping Type_ selection. For example, if you select _Picklist_, you must populate the _Picklist API_ and _Picklist Value_ fields.
   * The _Source Value_ cannot map to multiple target object values for a given _Import Field Mapping_.
7. Select **Save**.

[1]: #create-field-import-mappings
[2]: #create-mappings
[3]: #standard-mappings
[4]: #tabular-source
[5]: #field-import
[6]: #import-code
[7]: #tabular-data