Agentforce Platform | Update Record

Action Details

Considerations

• Only existing records that are searchable and User Interface API enabled can be updated by this action.
• This action only supports objects with layouts.
• The action only returns fields from the record’s page layout that can be updated or created. Read-only fields are filtered out even if requested by the user.
• Users must have permission to view and edit the record and fields they want to update. Users can update one record at a time.
• This action doesn’t support record creation. For example, users can’t ask the AI agent to log a call because that requires creating a record.
• This action only supports the editing of records by updating record fields and their corresponding values. Other types of record changes—such as cloning, merging, associating a related record, transferring account ownership, or submitting a quote—aren’t supported.
• This action can’t create a new field on an object’s layout. For example, if a user enters, “Update the service start date to 12/10/2024,” the request will fail if the Service Start Date field doesn’t already exist.
• If a user wants to edit a multi-select picklist, only one value is supported per update.
• In percent fields, there's no calculation of a percentage. The action assumes that the value the user entered is already a percentage value.
• Conversion calculations in currency fields aren’t supported. For example, if a field stores an amount in dollars and the user asks to update the amount to 500 euros, the value will be saved as 500 dollars.
• In numeric fields, only the shorthand notation for thousands (K), millions (M), and billions (B) is supported. For example, "2K" will be interpreted as “2000.” However, the values of numeric fields can’t be converted. For example, if a field is named Number of Years and the user tries to update the value to "36 months,” the value will be changed to "36 years" rather than "3 years."
• Updates from a related record aren't supported for many-to-many relationships. For example, users can’t make a request such as: “Remove the contact John Smith from the Acme opportunity.”
• Users can’t append a value to an existing value in a field. The value the user provides overwrites any existing value.
• When this action runs in Lightning Experience, it shows three standard buttons: Confirm, Edit Full Record, and Cancel. These buttons appear by default and can’t be configured.
  • Confirm applies the updates to the record.
  • Edit Full Record opens the standard record form in Lightning Experience, allowing users to manually edit field values before saving. In Agentforce Builder, the button appears in the preview conversation, but clicking it doesn’t open the form or update any values. Changes made in the builder aren’t saved.
  • Cancel discards the update request and leaves the record unchanged.