Loading
Feature degradation | Gmail Email delivery failureRead More
Set Up and Maintain Your Salesforce Organization
Table of Contents
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
          Data Model Management in Setup with Agentforce (Beta)

          Data Model Management in Setup with Agentforce (Beta)

          Use Agentforce to create custom objects, fields, and relationships in your org.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise, Performance, Unlimited, and Developer Editions with Foundations or Agentforce 1 Editions
          User Permissions Needed
          To use Setup with Agentforce:

          The required permissions for Setup with Agentforce. See Assign Required Permissions and Access for Setup with Agentforce (Beta).

          AND

          The required permissions for the task listed in the table.

          Note
          Note Setup with Agentforce is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement, if executed by Customer, and the Non-GA Credit Consumption term in the Product Terms Directory. Enabling this pilot or beta service consumes Data 360 credits and is at the Customer's sole discretion.

          You can start the conversation with a specific request for a supported task, such as one of the utterances in the following table. The agent tries to reuse any existing supported objects, fields, and relationships to fulfill the initial request. The agent shows the proposed data model, and you can make changes or proceed to create it.

          Agentforce can help you with these tasks and requests related to creating custom objects, fields, and relationships.

          Supported Task Example Requests Additional Required User Permissions
          Get information on supported tasks for data model management
          • “What can you do related to data model management?”
          • “How can you help me manage the data model?”
          None
          Create a custom object
          • “Can you help me create a custom object?”
          • “I need an object for Vendors.”
          • “Create a new custom object to track and manage book reviews.”
          Customize Application
          Create a custom object and fields
          • “Create a Project object with fields for Start Date, End Date, and Description.”
          • “Set up an Internal Asset object with fields for Serial Number (text, unique), Purchase Date (date), and Status (picklist).”
          Customize Application
          Create a custom field
          • “Can you help me create a new custom field?”
          • “Can you add a new field named Internal Referral to the Contact object? The field should be of data type checkbox.”
          • “Can you add a date field to Contact to track the contract expiration date?”
          • Add a picklist on Contact called Customer Status with values New, Active, Inactive.
          Customize Application
          Create multiple custom objects with relationships
          • “Create a Project object with fields for Name, Start Date, and Budget, and a related Task object with fields for Name, Due Date, and Status. Make Task a child of Project.”
          • “Add a Course object and a Student object. Relate them by using a junction object called Enrollment, with fields for Enrollment Date and Status.”
          • “Set up a Department object with fields for Department Name and Location, and a related Employee object with fields for First Name, Last Name, and Job Title.”
          Customize Application
          Create multiple fields in a single request
          • “On Contact, add fields for Alternate Email (email), Work Phone (phone), and LinkedIn Profile (URL).”
          • “I need fields on Account for Region (text), Sales Rep Notes (long text area), and Renewal Date (date).”
          Customize Application

          Data Model Management Considerations

          • These data types are supported for custom fields.
            • Checkbox
            • Currency
            • Date
            • Date/Time
            • Time
            • Email
            • Long Text Area
            • Lookup Relationship
            • Number
            • Percent
            • Phone
            • Picklist (limited scope)
            • Rich Text Area (HTML)
            • Text
            • Text Area
            • URL
          • All existing custom objects are supported for reuse and custom field configuration.
          • Only these standard objects are supported for reuse and custom field configuration.
            • Account
            • Asset
            • Campaign
            • Case
            • Contact
            • Contract
            • Lead
            • Opportunity
            • Order
            • Product2
            • Quotes
          • Only standard and custom picklist fields are supported. Multi-select or global picklist fields aren’t currently supported, so the agent won’t create or reuse these field types.
          • A proposed picklist field can have a maximum of 10 picklist values.
          • The data model output can have a maximum of 15 objects, including new custom objects, existing custom objects, and the supported standard objects. There's a maximum of 15 fields per object, including new custom fields and existing standard and custom fields on that object.
          • While data model discovery queries aren’t currently supported, you can use Object Manager to explore your org’s objects, fields, and relationships. For example, for queries like “Show me all the fields on the Contact object,” use Object Manager or a SOQL (Salesforce Object Query Language) query.
          • If your org contains more than 125,000 fields across custom objects and supported standard objects, the reuse of existing objects and field capabilities isn’t supported.
          • You can’t update or delete objects, fields, or relationships. Instead, use Object Manager to perform these operations.
          • Responses contain AI-generated object descriptions and field descriptions for existing objects and fields instead of showing the stored description. Existing object and field descriptions aren’t overwritten.

          Custom Object Defaults

          A new custom object has these defaults.

          • An AI-generated value for the Description field.
          • A Record Name field that has a Data Type of “Auto Number” and these attributes.
            • Record Name: <Object> ID
            • Display Format: “A-{0000}”, where A is the first character of the object
          • These optional features are enabled.
            • Allow Reports
            • Allow Activities
            • Allow in Chatter Groups

          Custom Field Defaults

          A new custom field has these defaults.

          • AI-generated values for the Help Text and Description fields.
          • An AI-generated field name and API name based on the field label. The name contains no special characters, and can have a number appended to it for uniqueness.
          • These defaults apply based on the custom field data type.
            FIELD DATA TYPE DEFAULT
            Checkbox Defaults to False.
            Currency
            • Length defaults to 16.
            • Decimal places defaults to 2.
            Number
            • Precision defaults to 12.
            • Scale defaults to 5.
            Percent
            • Length defaults to 18.
            • Decimal places defaults to 0.
            Text Length defaults to 255.
            Text Area (Long)
            • Length defaults to 255.
            • Number of visible lines defaults to 3.
            Text Area (Rich)
            • Length defaults to 32,768.
            • Number of visible lines defaults to 25.
            Lookup Relationship
            • The Related List Label defaults to the object’s plural label. For example, if you have a custom object with a label of Parking Lot, the lookup field’s Related List Label defaults to Parking Lots.
            • The Child Relationship Name defaults to the custom object’s plural label, but is formatted like the API Name. The name contains no special characters, and can have a number appended to it for uniqueness. For example, if you have a custom object with a label of Parking Lot, the lookup field’s Child Relationship Name defaults to Parking_Lots.
           
          Loading
          Salesforce Help | Article