---
sourceDocument: Yokohama Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-business-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Customize your field map configuration

# Customize your field map configuration {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create a custom field map configuration to map a field
in an Agile Development 2.0 table for Azure DevOps projects of a process type.

## Before you begin

* [Discover and import Azure DevOps projects](https://www.servicenow.com/docs/RFFkzVcY7a4HOUKotEmRSg "Discover and import all available Azure DevOps projects into Agile Development 2.0 to start using the integration between the two applications.").
* Role required: sn_ado_int.user
{#custom-field-map-config-azure-agile__ul_ks2_r1c_ckb}

## About this task

The following field types are supported for custom field map configuration:

* Number
* Select
* Text
* Date
* Identity
* Date time
* Reference
* List
{#custom-field-map-config-azure-agile__ul_um3_411_w4b}

## Procedure

1. Navigate to AllAgile Azure DevOps IntegrationAzure DevOps Instances.
2. Open your Azure DevOps instance record.
3. From the Process Mapping related list, open a process map for which you want to customize the map configuration.
4. From the Table maps related list, open a record to create a field map configuration for that table map.
5. From the Field Maps relates list, click New.
6. On the form, fill in the fields.  
   {#custom-field-map-config-azure-agile__table_s3l_xlt_bkb__entry__2}

   | Field | Description |
   |-|-|
   | Internal Field | Field name in Agile Development 2.0. |
   | Lookup Column Name | This field is required when you select a reference field as the internal field. For more information, see [Configuring a reference field in Azure DevOps](https://www.servicenow.com/docs/0UEXu61V2LBCDB0pMsAMiQ#configuring-a-reference-field "Understand how to configure a reference field while creating a new field map configuration."). |
   | Table Map | Table map in Agile Development 2.0, in which this field is created. This field is auto-populated based on the table map record you select. |
   | External Field | Field ID in Azure DevOps. |
   | External Field Name | Display name of the field in Azure DevOps. |
   [Table 1. Field Map form]

   {#custom-field-map-config-azure-agile__table_s3l_xlt_bkb}
7. Click Submit.
{#custom-field-map-config-azure-agile__steps_rgj_w1b_4kb}

## What to do next

1. Validate your new table map configuration by clicking Validate and fix mapping from your process map form.
2. From the Table maps related list, navigate to your new field map configuration. If the Valid column of your configuration shows:
   * true, validation of your map configuration is successful.
   * false, validation of your map configuration failed. Ensure that you enter the correct values for all fields and validate again.
   {#custom-field-map-config-azure-agile__ul_f2m_xmt_bkb}

{#custom-field-map-config-azure-agile__ol_qjd_tmt_bkb}  
Important:  
If your custom map configuration is invalid or if the required fields are not mapped for that work item, the export and import action does not work.

## Configuring a reference field in Azure DevOps {#ariaid-title2}

Understand how to configure a reference field while creating a new field map
configuration.
When you select a reference field for the Internal Field field, you must select a value for the Lookup Column Name field. The value from the Lookup Column Name
field is used during the import and export of work items between Azure DevOps and Agile Development 2.0.

During import, the integration application searches for the record in the reference table using the Lookup Column Name field. If the record is not found, the value in the work item will be empty in Agile Development 2.0.

*[\>]: and then