# Vault Loader Command Line Tool Reference

Use the command line arguments and parameters in this reference to load data to your Vault or extract data from your Vault in bulk. This article lists actions and parameters available in the Vault Loader Command Line Tool. For information on getting started with the Vault Loader Command Line Tool, including installation and authentication, see <a href="/en/gr/26627/">Using the Vault Loader Command Line Tool</a>. For information on using the Vault Loader Command Line Tool to manage your Vault's file staging, see the <a href="/en/gr/67334/">Vault Loader File Staging Command Line Tool Reference</a>.

For each CSV input file, the file contents must be in comma-separated value format, but the file extension can be either .CSV or .TXT.

## Create Documents

Before starting, upload document source files or renditions to <a href="/en/gr/67334/#upload-item">file staging</a>. If you do not provide source files, documents are created as placeholders. Prepare the <a href="/en/gr/26605/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -createdocument
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -createdocument <br>
 -csv docs_for_upload.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Update Documents {#update-documents}

This action updates document fields on existing documents using the values you provide in the CSV. Before starting, prepare the <a href="/en/gr/26605/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -updatedocuments
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -updatedocuments <br>
 -csv docs_for_upload.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Add Document Versions {#add-document-versions}

This action creates new versions for an existing document. Before starting, upload all source files to <a href="/en/gr/67334/#upload-item">file staging</a> and prepare the <a href="/en/gr/26911/#preparing-the-csv-input-file">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -createversions
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm"> java -jar VaultDataLoader.jar -createversions <br>
 -csv docs_for_upload.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Add Document Renditions {#add-document-renditions}

This action adds new renditions to existing documents. Before starting, upload all files to <a href="/en/gr/67334/#upload-item">file staging</a> and prepare the <a href="/en/gr/26915/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -createrenditions
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -createrenditions <br>
 -csv new_renditions.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Create Document Attachments

This action adds new attachments to existing documents. If the attachment already exists, Vault uploads the attachment as a new version of the existing attachment. Before starting, upload all files to file staging and prepare the <a href="/en/gr/67267/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        -createdocumentattachments
      </p>
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <p>
        <code>java -jar VaultDataLoader.jar -createdocumentattachments</code>
      </p>
      <p>
        <code>-csv new_attachments.csv</code>
      </p>
      <p>
        <code>-m vault_vph_fields.csv</code>
      </p>
    </td>
  </tr>
</table>

## Delete Document Attachments

This action removes attachments from existing documents. Before starting, prepare the <a href="/en/gr/67267/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        -deletedocumentattachments
      </p>
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <p>
        java -jar VaultDataLoader.jar -deletedocumentattachments
      </p>
      <p>
        -csv attachments_to_delete.csv
      </p>
      <p>
        -m vault_vph_fields.csvs
      </p>
    </td>
  </tr>
</table>

## Create Document Relationships

This action creates new document relationships using details from the CSV file you provide. Before starting, prepare the <a href="/en/gr/43263/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -createrelationships
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -createrelationships <br>
-csv supporting_docs_2017.csv</code>
    </td>
  </tr>
</table>

## Export Document Relationships

This action exports document relationship metadata.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -exportrelationships
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -type [TYPE]
      </p>
      <p>
        -subtype [SUBTYPE]
      </p>
      <p>
        -classification [CLASSIFICATION]
      </p>
      <p>
        -noneditable
      </p>
      <p>
        -headers
      </p>
      <p>
        -where [WHERE]
      </p>
      <p>
        -columns [COLUMNS]
      </p>
    </td>
    <td>
      <p>
        <code class="sm">java -jar VaultDataLoader.jar createrleationships <br>
-exportrelationships<br>
-csv supporting_doc_relationships.csv<br>
-type References<br>
-where "product__v='wonderDrug'"</code><code class="sm"><br>
 -columns created_by__v</code>
      </p>
    </td>
  </tr>
</table>

## Delete Document Relationships

This action deletes existing document relationships identified in the CSV file. Before starting, prepare the <a href="/en/gr/43263/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -deleterelationships
    </td>
    <td>
      -csv [CSV]
      <p>
        -includefields
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -deleterelationships<br>
 -csv delete_supporting_doc_relationships.csv</code>
    </td>
  </tr>
</table>

## Update Document Roles {#update-document-roles}

This action updates the users assigned to roles on specific documents. Before starting, prepare the <a href="/en/gr/26613/#preparing">CSV input files</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -updateroles
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -updateroles <br>
 -csv new_doc_roles.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Remove Users from Document Roles

This action removes users from roles on specific documents. Before starting, prepare the <a href="/en/gr/26613/#preparing">CSV input files</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -deleteroles
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -deleteroles <br>
-csv remove_from_doc_roles.csv <br>
-m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Export Documents

This action exports document field values, renditions, and/or source files for all documents or documents that meet your criteria. Extracted metadata uses the specified CSV file. Exported files go to your Vault's file staging. You can also use this action to export document field names as column headers without data.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -exportdocuments
    </td>
    <td>
      -csv [CSV]
      <p>
        -type [TYPE]
      </p>
      <p>
        -subtype [SUBTYPE]
      </p>
      <p>
        -classification [CLASSIFICATION]
      </p>
      <p>
        -headers
      </p>
      <p>
        -columns [COLUMNS]
      </p>
      <p>
        -source
      </p>
      <p>
        -renditions
      </p>
      <p>
        -allversions
      </p>
    </td>
    <td>
      <p>
        <code class="sm">java -jar VaultDataLoader.jar <br>
 -exportdocuments <br>
 -csv doc_extract.csv <br></code> <code class="sm">-source<br>
 -type Resources<br>
 -where "product__v='wonderDrug'"<br>
 -columns created_by__v,title__v</code>
      </p>
    </td>
  </tr>
</table>

### Exporting Source Files & Renditions

When exporting files using _-renditions_ and/or _-source_, Vault Loader can only export 2,000 files in a single action. You can refine your export by document type or using the _WHERE_ clause. When an export includes documents with multiple rendition types and you include _-renditions_, the CSV output includes a separate row for each rendition type.

## Create Users {#create-users}

This action creates new users using details from the CSV file you provide. Before starting, prepare the <a href="/en/gr/26609/#preparing-csv">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -createusers
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -createusers <br>
 -csv user_onboarding.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Update Users {#update-users}

This action updates details for existing users using the CSV file you provide. Before starting, prepare the <a href="/en/gr/26609/#preparing-csv">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -updateusers
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -updateusers <br>
 -csv user_update.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Upsert Users {#upsert-users}

This action creates new users and updates details for existing users using the CSV file you provide. Before starting, prepare the <a href="/en/gr/26609/#preparing-csv">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -upsertusers
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
      <p>
        -idParam [FIELD]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -upsertusers <br>
 -csv user_update.csv <br>
 -m vault_vph_fields.csv<br>
</code>
    </td>
  </tr>
</table>

## Export Users

This action exports user metadata.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -exportusers
    </td>
    <td>
      -csv [CSV]
      <p>
        -columns [FIELD]
      </p>
      <p>
        -where [WHERE]
      </p>
      <p>
        -headers
      </p>
      <p>
        -noneditable
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -exportusers <br>
 -csv users_12-15-15.csv<br>
 -noneditable<br>
 -where "active__v='false'"</code>
    </td>
  </tr>
  <tr>
    <td>
    </td>
    <td>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -exportusers<br>
 -csv users_names.csv<br>
 -columns first_name__v,last_name__v</code>
    </td>
  </tr>
</table>

## Create Groups {#create-groups}

This action creates new groups using details from the CSV file you provide. Before starting, prepare the <a href="/en/gr/26611/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -creategroups
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -creategroups <br>
 -csv group_import.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Update Groups {#update-groups}

This action updates existing groups using details from the CSV file you provide. Before starting, prepare the <a href="/en/gr/26611/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -updategroups
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -updategroups <br>
 -csv group_update.csv <br>
 -m vault_vph_fields.csv<br>
</code>
    </td>
  </tr>
</table>

## Upsert Groups {#upsert-groups}

This action updates existing groups using details from the CSV file you provide. Before starting, prepare the <a href="/en/gr/26611/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -upsertgroups
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
      <p>
        idParam [FIELD]
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -upsertgroups <br>
 -csv group_import.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Export Groups

This action exports group metadata.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -exportgroups
    </td>
    <td>
      -csv [CSV]
      <p>
        -columns [FIELD]
      </p>
      <p>
        -headers
      </p>
      <p>
        -noneditable
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar -exportgroups <br>
 -csv groups_2015.csv<br>
 -noneditable</code>
    </td>
  </tr>
</table>

## Export Object Records {#retrieve-object-records}

This action exports record metadata for a specific object.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -export [OBJECT NAME]
    </td>
    <td>
      -csv [CSV]
      <p>
        -where [WHERE]
      </p>
      <p>
        -columns [FIELD]
      </p>
      <p>
        -headers
      </p>
      <p>
        -noneditable
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -export product__v <br>
 -csv prod_exp.csv <br>
 -where "name__v like 'Ad%'" <br>
 -columns name__v</code>
    </td>
  </tr>
  <tr>
    <td>
    </td>
    <td>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -export product__v<br>
 -headers</code>
    </td>
  </tr>
</table>

## Create Object Records {#create-object-records}

This action creates new object records for a specific object. Before starting, prepare the <a href="/en/gr/26607/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td style="width: 193px;">
      <strong>Action</strong>
    </td>
    <td style="width: 203px;">
      <strong>Parameters</strong>
    </td>
    <td style="width: 569px;">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td style="width: 193px;">
      -create [OBJECT NAME]
    </td>
    <td style="width: 203px;">
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
      <p>
        -recordmigrationmode
      </p>
    </td>
    <td style="width: 569px;">
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -create product__v <br>
 -csv new_prods.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Update Object Records {#update-object-records}

This action updates existing object records with data from the provided file. Before starting, prepare the <a href="/en/gr/26607/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -update [OBJECT NAME]
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
      <p>
        -recordmigrationmode
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -update product__v <br>
 -csv update_prods.csv <br>
 -m vault_vph_fields.csv</code>
    </td>
  </tr>
</table>

## Upsert Object Records {#upsert-object-records}

This action updates existing object records or creates new records from the provided file. Before starting, prepare the <a href="/en/gr/26607/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -upsert [OBJECT NAME]
    </td>
    <td>
      -csv [CSV]
      <p>
        -m [MAPPING]
      </p>
      <p>
        -idParam
      </p>
      <p>
        -recordmigrationmode
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -upsert product__v <br>
 -csv update_prods.csv <br>
 -m vault_vph_fields.csv<br>
 -idParam external_id__v</code>
    </td>
  </tr>
</table>

## Delete Object Records {#delete-object-records}

This action deletes existing object records identified in the CSV file. If deleting specific records, prepare the <a href="/en/gr/26607/#prepare">CSV input file</a>. If deleting all records, you don't need to provide an input file.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      -delete [OBJECT NAME]
    </td>
    <td>
      -csv [CSV]
      <p>
        -all
      </p>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -delete product__v <br>
 -csv prods_to_delete.csv</code>
    </td>
  </tr>
  <tr>
    <td>
    </td>
    <td>
    </td>
    <td>
      <code class="sm">java -jar VaultDataLoader.jar <br>
 -delete product__v <br>
 -all</code>
    </td>
  </tr>
</table>

<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>: When deleting all object records, the rowID in the generated success file displays -1 next to each deleted object record. This is an expected behavior.</p>
    </div>
  </div>
</div>



## Create Object Record Attachments {#create-object-record-attachments}

This action adds new attachments to existing object records. If the attachment already exists, Vault uploads the attachment as a new version of the existing attachment. Before starting, upload all files to <a href="/en/gr/67334/#upload-item">file staging</a> and prepare the <a href="/en/gr/67288/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        -createattachments [OBJECT NAME]
      </p>
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <p>
        <code>java -jar VaultDataLoader.jar -createattachments product__v</code>
      </p>
      <p>
        <code>-csv new_attachments.csv</code>
      </p>
      <p>
        <code>-m vault_vph_fields.csv</code>
      </p>
    </td>
  </tr>
</table>

## Delete Object Record Attachments {#delete-object-record-attachments}

This action deletes existing attachments from object records. Before starting, prepare the <a href="/en/gr/67288/#prepare">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        -deleteattachments [OBJECT NAME]
      </p>
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
      <p>
        -m [MAPPING]
      </p>
    </td>
    <td>
      <p>
        <code>java -jar VaultDataLoader.jar -deleteattachments product__v</code>
      </p>
      <p>
        <code>-csv attachments_to_delete.csv</code>
      </p>
      <p>
        <code>-m vault_vph_fields.csv</code>
      </p>
    </td>
  </tr>
</table>

## Assign Users & Groups to Object Record Roles {#assign-users-groups-roles}

This action assigns users and groups to object record roles with custom or matching sharing rules. Before starting, prepare the <a href="/en/gr/76401/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        -assignobjectroles [OBJECT NAME]
      </p>
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
    </td>
    <td>
      <p>
        <code>java -jar VaultDataLoader.jar -assignobjectroles object_name__c</code>
      </p>
      <p>
        <code>-csv assign_object_roles.csv</code>
      </p>
    </td>
  </tr>
</table>

## Remove Users & Groups from Object Record Roles {#remove-users-groups-roles}

This action removes users and groups from roles on object records with custom or matching sharing rules. Before starting, prepare the <a href="/en/gr/76401/#preparing">CSV input file</a>.

<table class="wbord">
  <tr>
    <td width="20%">
      <strong>Action</strong>
    </td>
    <td width="20%">
      <strong>Parameters</strong>
    </td>
    <td width="60%">
      <strong>Example</strong>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        -removeobjectroles [OBJECT NAME]
      </p>
    </td>
    <td>
      <p>
        -csv [CSV]
      </p>
    </td>
    <td>
      <p>
        <code>java -jar VaultDataLoader.jar -removeobjectroles object_name__c</code>
      </p>
      <p>
        <code>-csv remove_object_roles.csv</code>
      </p>
    </td>
  </tr>
</table>

## Parameters

The following parameters must be used with other arguments to modify how Vault processes a command:

<table class="wbord">
  <tr>
    <td width="35%">
      <strong>Parameter</strong>
    </td>
    <td width="65%">
      <strong>Description</strong>
    </td>
  </tr>
  <tr>
    <td width="20%">
      -all
    </td>
    <td width="20%">
      Use this flag with a delete action to indicate that the action should affect all records of the specified object.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -async
    </td>
    <td width="20%">
      Use this flag with any action to complete the operation asynchronously. With this flag, you will be able to immediately start a new operation. The command line tool will not display status messages on asynchronous operations, but will immediately return a job ID that enables you to later check the status.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -type [TYPE]<br> -subtype [SUBTYPE]<br> -classification [CLASSIFICATION]
    </td>
    <td width="20%">
      Use these flags to filter the results of an export operation by document type, subtype, and/or classification.
    </td>
  </tr>
  <tr>
    <td>
      -where [WHERE]
    </td>
    <td>
      Use this flag with an export action to filter the export based on a VQL query. The value must be a <a class="external-link " href="https://developer.veevavault.com/vql/#Where_Clause" target="_blank" rel="noopener">WHERE clause<i class="fa fa-external-link" aria-hidden="true"></i></a> wrapped in double quotation marks, such as <code>"product__v='wonderDrug'"</code>.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -headers
    </td>
    <td width="20%">
      Use this flag with an export action to export only field names as column headers. This can help you to create a template for CSV input files.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -columns [COLUMNS]
    </td>
    <td width="20%">
      Use this flag on an export action by specifying field names to limit the export to only those fields. Note that you cannot have spaces between columns names when specifying columns with the '-columns' flags.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -noneditable
    </td>
    <td width="20%">
      Use this flag on an export action to extract both editable and read-only fields. Note that including non-editable fields means that you cannot use the export as a template for CSV input files.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -idParam [FIELD]
    </td>
    <td width="20%">
      Use this flag on update, upsert, or delete actions to specify that items are identified in the CSV input file via an external ID, rather than the ID field.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -allversions
    </td>
    <td width="20%">
      Use this flag on an export documents action to include all document versions in your export.
    </td>
  </tr>
  <tr>
    <td width="20%">
      -includefields
    </td>
    <td width="20%">
      Use this flag with a load action to specify that Vault should include the input fields in the output success log.
    </td>
  </tr>
  <tr>
    <td>
      -recordmigrationmode
    </td>
    <td>
      Use this flag to create or update a record in a specific lifecycle state. When you set this flag, Vault skips sending out email notifications when tasks are assigned, reassigned, or completed for the user tasks in the batch. Additionally, Vault bypasses entry criteria, entry actions, event actions (create actions only), validation rules, and reference constraints.
    </td>
  </tr>
  <tr>
    <td>
      -documentmigrationmode
    </td>
    <td>
      <p>
        Use this flag with the following action and object types to create records in a specific state or state type. Also allows you to set the name, document number, and version number:
      </p>
      <ul>
        <li>
          Create documents
        </li>
        <li>
          Update documents
        </li>
        <li>
          Create document renditions
        </li>
        <li>
          Create document versions
        </li>
        <li>
          Create documents, versions, roles
        </li>
      </ul>
    </td>
  </tr>
</table>
