---
title: "Add document record fields - ODBC"
slug: "add-document-records-fields-odbc"
tags: ["Task topic"]
status: "update"
updated: 2026-10-05T12:01:57Z
published: 2026-10-05T12:01:57Z
canonical: "docs.staedean.com/add-document-records-fields-odbc"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add document record fields - ODBC

To each document record, add the data fields which values must be exchanged. For **ODBC** documents, set up the fields in line with naming in the external database. For **ODBC** documents, make sure the fields have the same type as in the external database. This topic explains how to add record fields to an **ODBC** document.

If fields are already initialized for, selected for, or copied to the record, you can review and complete the setup for these fields. To do so, skip step 6.

### Steps

1. Click **Connectivity** **studio - Integration Design**.
2. Click the **Documents** tab.
3. In the list, find and select the desired **ODBC** document.
4. Click **Edit**.
5. In the **Records** section, in the **Record** list, find and select the desired record.
6. On the **Fields** tab, click **New**.
7. For the applicable project, you can define a default **ODBC** connector to an external database. If the **Database** connection is active, and you selected an external table in the **Record** field, you can select fields from the external table. If no **Database** connection is active, enter a free-definable name. Usually, this is a field name as used in the external database.

In the **Field name** field, type a value.

> [!NOTE]
> **Note**
> 
> The value of this field cannot have spaces.
8. For the applicable project, you can define a default **Database** connector to an external database. If the **Database** connection is active, and you selected an external table in the **Record** field, you can select fields from the external table. The value, as entered in the **Field name** field, is the default value.

In the **Record** **table field** field, type a value.

> [!NOTE]
> **Note**
> 
> The value of this field cannot have spaces.
9. Indicate if the field is a key field for the record. Select the **Key field** check box.
10. Indicate if the field is mandatory to be filled. If on processing the document, the field has no value and **Mandatory** is set to:

  - **Yes**, an error is given, and the document is not processed.
  - **Warning**, a warning message is given, but the document is processed.
  - **No**, the document is processed.

In the **Mandatory** field, select an option.
11. Set the field length carefully. Make sure the number of characters is sufficient to contain the value. If you set the length too short, the value is truncated. In the **Length** field, enter a number.
12. Select the field type as defined in the external database. So, ODBC knows how to read or write the data of the field.

In the **Type** field, select an option.
13. Define the dimension type to indicate the Microsoft Dynamics AX 2012 table from which to read the dimensions.

In the **Dimension** field, select an option.

> [!NOTE]
> **Note**
> 
> Only use the dimension fields for migrations from Microsoft Dynamics AX 2012 to D365 F&SCM.
14. Enter the field of the Microsoft Dynamics AX 2012 table where the dimension is stored.

In the **Dimension** **field** field, enter or select a value.
15. Define the name of the dimension to be read from Microsoft Dynamics AX 2012.

In the **Dimension name** field, type a value.

> [!NOTE]
> **Note**
> 
> Only use the dimension fields for migrations from Microsoft Dynamics AX 2012 to D365 F&SCM.
16. Sub-task: Set external references for record.

  1. In the **Line details** section, set the external references for the record.

You can indicate which of the records fields contains the unique ID of the record in the external database. In this way, you link the external ID to the record ID.

In the **External reference** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> Usually, you only use this for an **ODBC** connection with CRM or if you use web services.
  2. You can indicate which of the records fields contains the revision of the record in the external database. In this way, you find and link the latest revision to the record ID.

In the **Revision field** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> You can only use this field in combination with the **External reference** field.

> [!NOTE]
> Note
> 
> You can only delete a record field if it is not used in a:
> 
> - Relation
> - Sorting
> - Range
> 
> When you delete a field and it is used in one of these cases, a warning message is shown.
> 
> To delete the field, you must first delete the dependent setup.