---
schema_version: "1"
id: 9922aafe6673baa7f67cdcfdec11b61361d9e010473260a13f1a98834068b018
title: Add the User Managed Field to the Trigger Handler Page Layout
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/eda_add_user_managed_field_to_trigger_handler_pl.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.eda_add_user_managed_field_to_trigger_handler_pl.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 506f499c033cf2cd1d314028ffa73974cf1f597787cb959b46e257b7915ccc9d
description: This article will walk you through adding the User Managed field to the Trigger Handler Page Layout in Education Data Architecture (EDA).
products:
  - Education
release: "264"
---
# Add the User Managed Field to the Trigger Handler Page Layout

This article will walk you through adding the User Managed field to the Trigger Handler Page Layout in Education Data Architecture (EDA).

In EDA version 1.37 we modified how EDA manages trigger handler objects and made it easier for developers building on top of EDA to take advantage of TDTM. Part of those changes included a field named "**Owned by Namespace**". **Owned by Namespace** is a text field that developers or admins can use to logically group their Trigger Handlers together.

EDA uses **Owned by Namespace** to manage its own Trigger Handlers. The field allows EDA to know if there were changes or updates, or even if a trigger handler was deleted during an upgrade. This means if a dev or admin adds a common value to **Owned by Namespace** for all of their Trigger Handlers they will be isolated from EDA or other packages using TDTM. This isolation means they will not need to protect their trigger handlers with **"User Managed"**.

If a Trigger Handler object does not have a value in **Owned by Namespace** the Trigger handler object can still be protected by the use of the **User Manage** field. This behavior has not changed. Setting **User Managed** on an EDA Trigger Handler will still allow users to override it and EDA will skip over the record during upgrade even if there were changes to the Trigger handler definition.

We recommend applying the **Owned by Namespace** field with a common value for all the Trigger Handler objects a developer has created. This gives them several advantages. First, using the **Owned by Namespace** field allows the developer to store the definitions in a class which can be saved in source control. Then they can pass their configuration into the EDA TDTM Global API and EDA will perform the processing for them.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/images/icon_important.png)

Important The **Owned by Namespace** and the **User Managed** field is hidden in any EDA org where the initial package version is 1.34 or lower and needs to be added to the Trigger Handler Page Layout.

This article will explain how to add these fields.

- **[Add the User Managed Field (Salesforce Classic Interface)](https://help.salesforce.com/s/articleView?id=sfdo.eda_add_user_managed_field_to_trigger_handler_pl.htm&release=264.0.0&type=5)**  
    Complete these steps to add the User Managed field in Salesforce Classic.
- **[Add the User Managed Field (Lightning Experience Interface)](https://help.salesforce.com/s/articleView?id=sfdo.eda_add_user_managed_field_to_trigger_handler_pl.htm&release=264.0.0&type=5)**  
    Complete these steps to add the User Managed field in Lightning Experience.

## Add the User Managed Field (Salesforce Classic Interface)

Complete these steps to add the User Managed field in Salesforce Classic.

1. Click **Setup**.
2. In the Quick Find box, enter objects, then select **Objects**.
3. In the list of objects, click **Trigger Handler**.
    
    ![Trigger Handler Hyperlink](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/education_data_architecture/images/usr_mgd_field_trigger_handler_link.png)
4. Scroll down to the Page Layouts related list and click **Edit**.
    
    ![Edit Hyperlink](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/education_data_architecture/images/usr_mgd_field_trigger_handler_layout.png)
5. Drag the **Owned by Namespace** and the **User Managed** field onto the page layout.
    
    ![Page Layout Editor](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/education_data_architecture/images/usr_mgd_field_eda_trigger_handler_ple.png)
6. Click **Save**.

## Add the User Managed Field (Lightning Experience Interface)

Complete these steps to add the User Managed field in Lightning Experience.

1. Click ![Setup](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/resources-product/images/setup.png), then click **Setup**.
2. Click the **Object Manager** tab.
    
    ![Object Manager tab](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/education_data_architecture/images/usr_mgd_field_obj_mgr_tab.png)
3. Click **Trigger Handler**.
4. Click **Page Layouts**.
5. Click the drop-down arrow to the right of the page layout name, then click **Edit**.
    
    ![Page Layout Assignment expanded to show Edit and Delete options.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/education_data_architecture/images/usr_mgd_field_page_layout_assignmt.png)
6. Drag the **User Managed** field onto the page layout.
    
    ![Page Layout Editor](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-education_data_architecture-264-0-0-production-enus/6bcf23e4-1d0f-4cd5-8405-b8e231f03ed0/education_data_architecture/images/usr_mgd_field_eda_trigger_handler_ple.png)
7. Click **Save**.

You can now either enable or disable any trigger and the "pushes" from new versions will not affect your customizations.

We hope this has helped!