Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Agentforce and Einstein Generative AI
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Manage Changes to Object-Based Types

            You are here:

            1. Salesforce Help
            2. Docs
            3. Quickstart Your Einstein Generative AI Solution

            Manage Changes to Object-Based Types

            You create object-based custom Lightning types in Prompt Builder to structure prompt template output. When you edit these types, you can’t modify certain field properties to avoid disrupting integrations. Modifications such as renaming fields, changing data types, deleting fields, or making optional fields required can cause integrations and references to fail.

            Required Editions

            Available in: Lightning Experience
            Available in: Enterprise, Performance, and Unlimited Editions with the Einstein for Platform, or Einstein or Agentforce for Sales or Service add-on, or Agentforce Foundations

            Breaking Changes

            To protect the integrity of your schema references, you can’t modify existing fields in these ways.

            • Data Type. You can’t change the data type, for example, from Text to Number, because integrations expect a specific data format.
            • Delete. You can’t delete an existing field referenced by integrations.
            • Field Name. You can’t rename an existing field because external references rely on the specific API name.
            • Required. You can’t make an existing optional field required. Making a field mandatory can break legacy data or integrations that don’t provide a value for that field.

            Safe Changes

            You can safely make these updates without disrupting dependencies.

            • Add new fields. You can add new fields to an existing custom Lightning type. To ensure backward compatibility, new fields default to optional with the Required checkbox disabled.
            • Make required fields optional. You can deselect Required to make a field less restrictive.
            • Update descriptions. You can modify descriptions to provide better clarity.
             
            Loading
            Salesforce Help | Article