Manage Table: Editor: Column Advanced Settings: Option List: Lookup
## Overview
When selecting [Department](/en/manual/dept), [Group](/en/manual/group), [User](/en/manual/table-management-choices-text-users), and 「Linked Column」, you can copy column values from the selected [Department](/en/manual/dept), [Group](/en/manual/group), [User](/en/manual/table-management-choices-text-users), or 「Linked Column」 into the current record. For example, when a deals table is linked to a customers table, you can copy columns such as the address and phone number from the customers table into the deals table. Images embedded in [Description Item](/en/manual/table-management-description) can also be copied. Combined with the [Auto post back](/en/manual/table-management-auto-postback) feature, values can be reflected immediately after a master record is selected.
## Limitations
1. The lookup feature can be configured on [Class Column](/en/manual/table-management-class), [Manager Column](/en/manual/table-management-manager), and [Owner Column](/en/manual/table-management-owner).
1. Cannot be used when the 「Multiple Selections」 feature is enabled.
1. [Comments Column](/en/manual/table-management-comments) and [Attachments Column](/en/manual/table-management-attachments) cannot be specified as From or To.
1. If a columns without "Read" permission is specified as From, an empty string will be copied.
1. Because the copied value is saved directly into the column, changes made in the parent table will not be reflected.
1. When using [Import](/en/manual/table-record-import) with the [Update record with the same key.](/manual/table-record-import-and-update) option, the lookup only fires when a column value has changed.
1. Does not work when [Department](/en/manual/dept), [Group](/en/manual/group), [User](/en/manual/table-management-choices-text-users), or 「Linked Column」 allow 「Multiple Selections」.
1. If an image is embedded in a [Description Item](/en/manual/table-management-description) specified as From, that image will also be copied. However, because the copied image inherits the access permissions of the source record, the image may not be displayed.
## Prerequisites
1. "Site administration permission" is required to configure this feature.
## Procedure
Specify a "link" in JSON format in the [Option List](/en/manual/table-management-choices-text). The syntax follows the same convention as [Manage Table: Editor: Column Advanced Settings: Option List: Filter, Sort, Display Format](table-management-choice-json).
## Configuration Example 1
In the example below, a link is made to SiteId 6. When a record is selected, classification A (ClassA) from SiteId 6 is copied to classification B (ClassB), classification B (ClassB) is copied to classification C (ClassC), status (Status) is copied to classification D (ClassD) with Type set to 1 so that the [Name displayed](/en/manual/table-management-label-text) rather than the value is copied, and DateA, CheckA, and DescriptionA are each copied to their respective columns.
##### JSON
```json
[
{
"SiteId": 6,
"Lookups": [
{
"From": "ClassA",
"To": "ClassB"
},
{
"From": "ClassB",
"To": "ClassC"
},
{
"From": "Status",
"To": "ClassD",
"Type": 1
},
{
"From": "DateA",
"To": "DateA"
},
{
"From": "NumA",
"To": "NumA"
},
{
"From": "CheckA",
"To": "CheckA"
},
{
"From": "DescriptionA",
"To": "DescriptionA"
}
]
}
]
```
## Configuration Example 2
In the example below, [Department](/en/manual/dept) are set as the [Option List](/en/manual/table-management-choices-text). When an [Department](/en/manual/dept) is selected, the DeptsId is copied to ClassE.
##### JSON
```json
[
{
"TableName": "Depts",
"Lookups": [
{
"From": "DeptCode",
"To": "ClassE",
"Type": 0
}
]
}
]
```
## Configuration Example 3
In the example below, [Group](/en/manual/group) are set as the [Option List](/en/manual/table-management-choices-text). When a [Group](/en/manual/group) is selected, the [Description](/en/manual/table-management-column-description) is copied to ClassE.
##### JSON
```json
[
{
"TableName": "Groups",
"Lookups": [
{
"From": "Body",
"To": "ClassE",
"Type": 0
}
]
}
]
```
## Configuration Example 4
In the example below, [User](/en/manual/table-management-choices-text-users) are set as the choice list. When a [User](/en/manual/table-management-choices-text-users) is selected, the organization name is copied to ClassE, the Description is copied to descriptionA, and the email address is copied to ClassM.
##### JSON
```json
[
{
"TableName": "Users",
"Lookups": [
{
"From": "Dept",
"To": "ClassE",
"Type": 1
},
{
"From": "Body",
"To": "DescriptionA"
},
{
"From": "MailAddresses",
"To": "ClassM"
}
]
}
]
```
## Configuration Example 5
In the example below, 「Groups」 are set as the [Option List](/en/manual/table-management-choices-text). When a [Group](/en/manual/group) is selected, the group name is copied to ClassE. If classification E already has a value, it will not be overwritten; the copy only occurs when ClassE is empty.
##### JSON
```json
[
{
"TableName": "Groups",
"Lookups": [
{
"From": "GroupName",
"To": "ClassE",
"Type": 0,
"Overwrite": false
}
]
}
]
```
## Configuration Example 6
In the example below, [Group](/en/manual/group) are set as the [Option List](/en/manual/table-management-choices-text). When a [Group](/en/manual/group) is selected, the group name is copied to ClassA, overwriting any existing value in ClassA.
##### JSON
```json
[
{
"TableName": "Groups",
"Lookups": [
{
"From": "GroupName",
"To": "ClassA",
"Type": 0,
"OverwriteForm": true
}
]
}
]
```
## Configuration Reference
| No | Option | Description |
|:---|:---|:---|
| 1 | From | Specifies the database [column name](/en/manual/dev-column-name) in the source [Table](/en/manual/table). |
| 2 | To | Specifies the database [column name](/en/manual/dev-column-name) in the destination [Table](/en/manual/table). |
| 3 | Type | Specify "0" to copy the value; specify "1" to copy the [Name displayed](/en/manual/table-management-label-text). Type is optional. The default when omitted is "0". |
| 4 | Overwrite | Specify "false" to skip copying when the column specified in To already has a value, allowing the copy only when the column is empty. Overwrite is optional. The default when omitted is "true". |
| 5 | OverwriteForm | Specify "true" to always copy the value to the column specified in To. OverwriteForm is optional. The default when omitted is "false". Note that this will overwrite even values entered manually by the user. |
## Additional Details
1. When specifying a [Status Item](/en/manual/table-management-status) or [Class items](/en/manual/table-management-class) that distinguishes between a value and a [Name displayed](/en/manual/table-management-label-text) as From, the Type setting is important. If To also distinguishes between a value and a [Name displayed](/en/manual/table-management-label-text), specify "0"; if you want to copy the display name as a plain string, specify "1".
## Supported Versions
| Supported Version | Notes |
|:---|:---|
| 1.1.27.0 and later | Feature added |
| 1.2.2.0 and later | Lookup support added for [Department](/en/manual/dept), [Group](/en/manual/group), and [User](/en/manual/table-management-choices-text-users) |
| 1.3.10.0 and later | Overwrite control switch (Overwrite) added |
| 1.4.13.0 and later | [Manager Column](/en/manual/table-management-manager) and [Owner Column](/en/manual/table-management-owner). added as supported column types |
## Related Information
<div id="ManualList"><ul><li><a href="/en/manual/table">Table Function</a><span>08.13.2024 up</span></li>
<li><a href="/en/manual/table-record-import">Table Function: Importing Records</a><span>09.22.2025 up</span></li></ul></article>
<ul><li><a href="/en/manual/table-management-status">Manage Table: Items: Status</a><span>12.09.2025 up</span></li>
<li><a href="/en/manual/table-management-manager">Manage Table: Items: Manager</a><span>12.09.2025 up</span></li>
<li><a href="/en/manual/table-management-owner">Manage Table: Items: Owner</a><span>12.09.2025 up</span></li>
<li><a href="/en/manual/table-management-class">Manage Table: Items: Class</a><span>12.09.2025 up</span></li>
<li><a href="/en/manual/table-management-description">Manage Table: Items: Description</a><span>12.09.2025 up</span></li>
<li><a href="/en/manual/table-management-attachments">Manage Table: Items: Attachments</a><span>03.25.2026 up</span></li>
<li><a href="/en/manual/table-management-comments">Manage Table: Items: Comments</a><span>12.09.2025 up</span></li></ul></article>
<ul><li><a href="/en/manual/table-management-label-text">Table Management: Editor: Item Detail Settings: Display Name</a><span>08.13.2024 up</span></li>
<li><a href="/en/manual/table-management-column-description">Manage Table: Editor: Column Advanced Settings: Description</a><span>05.26.2025 up</span></li>
<li><a href="/en/manual/table-management-choices-text">Manage Table: Editor: Column Advanced Settings: Option List</a><span>11.27.2025 up</span></li>
<li><a href="/en/manual/table-management-choices-text-depts">Table Management: Editor: Item Detail Settings: Option List: Departments</a><span>08.13.2024 up</span></li>
<li><a href="/en/manual/table-management-choices-text-users">Table Management: Editor: Item Detail Settings: Option List: User</a><span>08.13.2024 up</span></li>
<li><a href="/en/manual/table-management-auto-postback">Table Management: Editor: Item Detail Settings: Auto Postback</a><span>08.13.2024 up</span></li></ul></article>
<ul><li><a href="/en/manual/dept">Department Management Function</a><span>08.13.2024 up</span></li></ul></article>
<ul><li><a href="/en/manual/group">Group Management Function</a><span>10.08.2024 up</span></li></ul></article>
<ul><li><a href="/en/manual/dev-column-name">Correspondence of Column name and Name in the system in the Database</a><span>12.17.2025 up</span></li></ul></article></div><input id="SearchTextHidden" type="hidden" value="" />
