Last date modified: 2026-Nov-05
Importing an RDO load file
You can import Relativity's dynamic objects (RDO) for use in Relativity applications. The workflow for RDO data import follows the same general guidelines as those for document load file imports.
References
We recommend referring to the following information when importing RDO load files:
- Express Transfer overview, if you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer.
- Import/Export load file specifications and Data upload size limitation for more information regarding import of load files. Also, see General recommendations for structured data import and export jobs. Also see Load file import recommendations.
Importing RDO load file workflow
To import RDO data:
- Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
- On the Import/Export Job page, click New Import/Export Job to start a new job.
- On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Processed) Data workflow box.
If you activated Express Transfer, the Express Transfer section displays a status of Active. See Activating and deactivating Express Transfer for more information. - On the Choose the Load File Type dialog, click the RDO box to import a load file to your workspace.

- If Express Transfer is not Active, skip this step. If it is Active, go to Select data to Import fields.
- Complete fields on the Choose Load File and Location dialog, then click Continue. For more information, go to Choose Load File and Location fields. Also, see Import/Export load file specifications for details on load files.
- Select delimiters and encoding values of the load file for the import on the Load File Settings dialog, then click Continue. For more information, go to Load File Settings fields.
- On the Load File Field Mappings dialog, select the load file fields to import and map them to the workspace fields, then click Continue. For more information, go to Load File Field Mappings options.
- Configure your import on the Import Settings dialog. For more information, go to Import Settings fields.
- (Optional) Click Download Profile (.ie) on the Import Settings dialog to download the job configuration settings entered to an .ie file on your computer. This way they can be reused for other jobs.
- (Optional) Click Precheck Load File on the Import Settings dialog to check for errors before importing the load file. For details, see Pre-check Load File optional step.
- Click the Import button to start the importing process.
- Review the importing progress on the Overview tab on the Importing dialog. Real-time details regarding the number of transferred files and data size being processed are displayed during the Uploading and Extracting steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the importing process is complete.If you used Import/Export in web only mode, meaning Express Transfer was not active, do not close the Importing dialog until after the Uploading step has successfully completed. Closing the dialog before the Uploading step completes terminates the data transfer (upload) process.

- Go to the Job Settings tab on the Importing dialog to review the job configuration settings. If needed, select Download Profile (.ie) to download the job configuration settings entered to an .ie file on your computer. This way they can be reused for other jobs. You can also select Download Field Mapping (.csv) to download the file with field mapping.

- If no errors were found in the load file, go to the next step. If errors were found, go to Errors tab on the Importing dialog.
- Click Finish to close the dialog.
You can review the Import/Export Job page to see more information about the job. Refer to
For more information on where Import/Export saves files, see the Community article Import/Export: Where Files Are Saved By The Import/Export Application.
When a job is running using Express Transfer, you can close the Import/Export application. The transfer job continues without interruption. You can monitor the progress and history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You do not have to be logged in to Relativity aiR to view information within the Express Transfer application.
Select data to Import fields
Before importing RDO load files with Express Transfer activated, consider the following:
- When Express Transfer is active:
- You should not zip data for importing.
- It uploads only files linked in the selected load file, regardless of their location.
- It ignores mismatches in upper and lower case between file paths in the load file and the actual file names.
- It supports load files with relative paths, absolute paths, and UNC paths. You can mix path types in a single load file.
- You can choose only one folder with a load file to transfer.
- File names must be 200 characters or fewer, including the extension.
- We recommend using a local drive instead of a mapped or external drive to avoid potential slowness and connection issues with the file import process. Also, see Data transfer performance considerations.
If you are importing RDO load files with Express Transfer active, you can do the following in the Select data to Import dialog:
- Click Local Folder to browse to your local drive and select the folder with the files that you want to upload. For universal naming convention (UNC) paths, you can copy and paste the path into the Select Folder address bar in the dialog box to access the desired folder. For example, \\ServerName\SharedResourceName\FilePath.
- Click Staging Load File to select a load file from the StructuredData folder in Staging.
- Accessing Staging Load File requires Allow Staging Import permissions. See Permissions for more information.
- If you choose to import load file data from Staging, the load file and all linked files are copied to the destination located outside your Staging Area. After the import is completed, you can clean up the source data in Staging.
Choose Load File and Location fields
- Job Name—provide a descriptive job name so that you can identify and track that job on the Import/Export Job page. The Job name field accepts up to 50 characters.
- Relativity Object Type—select the Relativity object type from the drop-down list that you want to import data into.
- Profile—the job configuration settings that you saved to a profile file (.ie or .kw*). You can reuse a profile for future jobs that use the same or similar settings. Reusing a profile is intended to reduce time and data entry errors when mapping fields. You can use .ie profiles only in Import/Export.
- None—select this option if you do not want to use a profile for this import or if you intend to create a new profile based on the settings entered in the upcoming steps. You can save the profile settings later to an .ie file using the Download Profile (.ie) button.
- From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie file) or an existing .kw* profile, created in the former Relativity Desktop Client application, to reuse the job settings for this workflow. Use the drag and drop feature or browse for a file to choose it. All job settings provided within the selected profile file can be automatically entered where applicable in the succeeding workflow dialogs.
- Regional Settings (Date and Time)—select the format for imported date and time data. A preview of the chosen format appears below the selection. The setting selected remains for all future jobs until you choose another one from the list or until you clear your browser cache. When browser cache is cleared, the setting reverts to the US date and time by default.
- Load File—use the drag and drop feature or click browse for a file to select load file with RDO data from your local drive.
- Choose From Staging—select a load file from the StructuredData folder in Staging. Your load file data must not be zipped. You can choose only unzipped load file data from Staging.
- Include Native & Text—select this option to include native and text files. The Include Native & Text option is not available for image or production import workflows as there are no native files included in Opticon-formatted (.opt) files.
- Native & Text—if Include Native & Text was selected, use the drag and drop feature or click browse for a file to select the zipped native and text file from your local drive. See ZIP archive with extracted text and natives
- (Optional) Notification Addresses—enter the email addresses of the people you want to notify after the job completes, fails, or is canceled.
Load File Settings fields
The File Column Headers Preview pane helps you choose the proper settings.
- File Encoding—select an encoding format for the load file. Consult your processing vendor or department to determine the correct encoding option, if necessary.
The File Column Headers Preview pane automatically updates when you select the File Encoding type. Because the load file is parsed based on the delimiter set, you may need to check delimiters used in the load file if the column headers are not lined up correctly. Determine the delimiters used in the file, and then select them in the delimiters section of this tab. - First Line Contains Column Names toggle—select this option if the first line contains column names.
- Select the delimiters and encoding values used by your load file:
- Column—select the character used to separate columns.
- Quote—select the character used as the text qualifier.
- Newline (Long Text Fields)—select the character used to indicate the end of a line in any extracted text or long text field.
- Multi-Value—select the character used to separate choices within a field.
- Nested Value—select the character used to separate the different levels of a multi-choice hierarchy.
Load File Field Mappings options
You can map fields on the Load File Fields Mappings dialog using:
- Auto Map Fields button to automatically map fields.
- The fields from the load file are mapped to any existing fields of the exact same name in the workspace. Any fields without a match display "Choose..." in the Workspace Fields column. You need to select one from the drop-down list. To search for a field in the list, begin typing the desired field name and matching search results are displayed for selection.
- Consider the following when auto-mapping fields:
- Case is not taken into account for the mapping. For example, a field named "email" in the load file would map to a field named "Email" in the workspace.
- Spacing is taken into account. For example, in a two-word field name, if there is one space between words in the workspace field, and two spaces between words in the load file field, the fields are not mapped.
- Characters are mapped only to themselves. For example, an underscore is only mapped to another underscore, not to a space.
- Only fields matched or those with additional settings selected are loaded into the workspace. Other fields in the Load File Fields and Workspace Fields are ignored. You must always match the identifier field for the load file.
- Map with AI button to map similarly named fields when field names in the load file do not match precisely field names in the workspace.
- Consider the following when mapping fields with AI:
- Your data is not used for training and is not sent outside the Relativity aiR infrastructure.
- Fields are mapped based on the similarities in the meaning of fields’ names.
- Fields can be mapped automatically when the name meanings are strongly similar.
- The Review label appears for the mappings that may require your attention.
- Fields remain unmapped if the AI model cannot understand the meaning of the field name, or the name similarities are below the threshold. If you want to map these fields, select a corresponding field from the Workspace Fields list or create a new workspace field.
- Consider the following when mapping fields with AI:
- Workspace Fields column to manually map the load file fields to the existing workspace fields. Use the Filter box to search for field names.
Depending on your workflow, complete the following additional options available on this dialog:
- Export to CSV button—click to save the field mapping configuration to a .csv file on your local drive. You can select this option only before you run the job.
- Create Field button—click if you want to create a new workspace field. Import/Export currently supports creating the following document object field types. If you need to define advanced field settings, create a field directly from the Fields tab. For more information, go to Fields.
- Currency
- Date
- Decimal
- Fixed-Length Text
- Long Text
- Multiple Choice
- Single Choice
- User
- Whole Number
- Yes/No
- Sort by button—click to select your preferred sorting option:
- Default (A-Z)—sorts all rows in alphabetical order, based on the load file field names.
- Mapped on top—brings the mapped fields to the top and sorts them in alphabetical order.
- Unmapped on top—brings the unmapped fields to the top and sorts them in alphabetical order.
- Review on top—brings the mapped fields which require review to the top and sorts them in alphabetical order.
- Load File Sample column—presents read-only example data from the load file fields.
- Load File Fields column —displays the field names from the load file. Use the Filter box to search for field names.
- Additional Field Settings column—to enable additional field settings, click the Choose down arrow in this column to select the additional field as follows:
- Text File—select this option if the mapped Long Text field contains a relative path, absolute path, or UNC path to a text file. Then, select the File Encoding type for the file. If using absolute or UNC paths, you must activate Express Transfer before starting the import job. This field was renamed from Extracted Text because it now applies to any Long Text field.
- Folder Information column—select this option if you want to use a metadata field to build the folder structure for the workspace.
- Native File—select this option if the field from your load file contains a relative path, absolute path, or UNC path to the native files. If using absolute or UNC paths, you must activate Express Transfer before starting the import job.
Import Settings fields
On the dialog, configure your import job by selecting from which line number you want the load file to begin importing and how you want to import the records.
- Start Line—select the line number in the load file where you want the import process to begin. The default value is set to 0, which results in loading the entire load file.
- Import Mode—choose how you want the records to be imported.
- Append Only—loads only new records.
- Append/Overlay—adds new records and overlays data on existing records. If selected, then you must assign a unique identifier in the Overlay Identifier field that will be used to overlay data in the workspace. This field acts as a link indicating to Relativity aiR where to import the data. For Append/Overlay and Overlay Only, if a blank metadata field exists in the load file, .dat or .csv, the blank value overlays (removes) any existing value that may reside in the corresponding mapped field.
- Overlay Only—updates existing records only. If selected, then you must include an Overlay Identifier next.
- Overlay Identifier—if either Overlay Only or Append/Overlay mode is selected, assign the unique identifier that is used to overlay data in the workspace. This field acts as a link indicating to Relativity aiR where to import the data.
Pre-check Load File optional step
You can click Precheck Load File option on the Import Settings dialog to run a validation process on the load file to check for errors before importing it. For more details, refer to Pre-check Load File.
All detected errors are displayed in the Pre-check window. Click the down arrow next to any error message to view its details. If you want to correct the errors in the source files and repeat the importing steps, click Cancel . Otherwise, go to the next step to import the load file with errors and correct them later. During precheck, Import/Export validates the following:
- Date format
- Field type
- Field length
- Number of load file cells
- Number of folders and choice fields
- File paths for natives and extracted text. The precheck checks 1,000 random lines across the whole load file.
Errors tab on the Importing dialog
If the load file contains errors, click the Errors tab on the Importing dialog to view them. Next, do one of the following:
- To proceed without correcting the errors, click Close.
- To download the error report as a .csv file, select Errors & Warnings Report (.csv). The report lists all errors and warnings for the import job. You can download in from any tab on the Importing dialog.
- To correct the errors manually:
- Select Download Error Load File.
- Review the errors and correct them as needed.
- When you have finished, upload the file with the corrected data by clicking Select on the Importing dialog next to New Load File.
- Navigate to the load file on your local drive to select it.
- Once selected, click Import to import the job with corrected data.
- You can only correct documents included in the original load file. If you need to add missing documents, create a new import job.
- Only records that imported without errors will appear in the workspace.
On this page