---
title: "Create Link Storage Values"
description: "Create Link Storage Values"
keywords: "Create Link Storage Values how to create a link storage entry LS"
url: "https://myrapidi.com/wiki/create_link_storage_values"
locale: "en"
published: "2018-03-01T12:51:14Z"
modified: "2025-12-17T10:47:14Z"
---

Creating a Link Storage is the first step in defining how Rapidi will store and match keys between your systems. A Link Storage represents **one specific set of links** (e.g., ERP Customer Number ↔ CRM Account Id). You can create **as many Link Storages as needed** , one for each type of record you want to synchronize.

Your browser does not support the video tag.
  
  
When you create a Link Storage, you are essentially telling Rapidi:

- _What kind of keys you want to store_
- _How each side is called (left and right)_
- _How to separate multi-field keys_
- _Which system/tables/fields belong to each side_

After that, Rapidi will dynamically populate and maintain these values during runtime.

Below is a clear explanation of each field you must configure.

**1. Code**

A short, unique identifier (UPPERCASE letters and numbers only) that identifies this Link Storage. You will use this code in Transfers and in LSLookup formulas.

**Examples:**

- CUST
- CUST\_UK
- ITEM
- VENDOR

**Tip:**  
 Choose a code that reflects the purpose — this makes formulas and troubleshooting easier.

**2. Description (Left Column Header)**

 A description of what kind of values appear in the **first / left column** of the Link Storage.This text becomes the **actual column heading** in the Link Storage Values screen. It should clearly indicate the meaning of the key stored on this side.

**Examples:**

- "NAV Customer Numbers"
- "GP Item Numbers"
- "ERP Vendor IDs"

**3. Description 2 (Right Column Header)**

 A description of what kind of values appear in the **second / right column**. This becomes the column title for the right side and helps clarify the relationship.

**Examples:**

- "Salesforce Account Ids"
- "CRM Product Ids"
- "HubSpot Contact Record IDs"

**4. LinkField Separator**  
  
A character used to separate field values when a key consists of multiple fields. Some systems (like ERP documents) use composite keys such as: Document Type + Document Number + Line Number. Rapidi needs a separator so it can store and later re-identify these combined values correctly.

**Default:**  
 #

### **Defining the Content of Each Column**

Once the Link Storage is saved, you move on to defining what belongs in each of the two columns.This tells Rapidi:

- Which **connection** the values come from
- Which **table** they belong to
- Which **fields** together form the unique key

You can add **one or multiple** definitions per column (useful for systems with different tables or objects representing the same entity). Below are the fields you configure when adding a new entry to either the left or right column.

**1. Connection**

The Rapidi Connection from which this side’s data comes. Rapidi needs to match the Transfer’s Source or Destination Connection with the correct side of the Link Storage.

**Example:**

- NAV
- GP
- SALESFORCE

**2. Table Name**  
  
The name of the table or object that holds the key fields for this side. Rapidi compares this to the Transfer’s Source Table or Destination Table when running.

**Examples:**

- Customer
- Item
- Account
- Product2
- SalesHeader

**Note:**  
 This must match exactly the table/object name used in the Transfer.

**3. Link Fields**  
  
One or more fields that form a unique key for this table. Rapidi uses these fields to build the key value that will be stored in the Link Storage.  
  
**Examples (single-field key):**

- No
- CustomerNumber
- AccountId

**Examples (multi-field key):**

- DocumentType, DocumentNo
- LineType, LineNumber

**How Rapidi stores it:**  
  
 If multiple fields are used, they are automatically joined using the LinkField Separator (e.g., SO#12345).