What should An Agentforce consider when using related list merge fields in a prompt template associated with an Account object in Prompt Builder?

When using related list merge fields in Prompt Builder, it is crucial to understand the limitations regarding data relationships. The Activities related list (which combines Tasks and Events) cannot be used because its underlying relationship fields (WhatId and WhoId) are polymorphic. This means they can point to multiple different types of objects (e.g., Account, Contact, Opportunity). Prompt Builder's merge field functionality does not support traversing these complex, multi-object relationships, and therefore, the Activities related list is explicitly excluded from use in prompt templates.

B. If person accounts have been enabled, merge fields will not be available for the Account object.

This is incorrect. Prompt Builder is compatible with Person Accounts, and merge fields for the Account object remain available for use in prompt templates.

C. Prompt generation will yield no response when there is no related list associated with an Account in runtime.

This is incorrect. If a prompt template references a related list that has no records for a specific Account at runtime, the merge field resolves as empty, but the rest of the prompt is still generated. The process does not fail or yield no response.

1. AGENTFORCE Official Documentation

"Prompt Builder Developer Guide

" Section: Merge Field Syntax and Limitations.

Document ID: PB-DEV-2024-1

Page 42

Paragraph 3: "Related list merge fields do not support polymorphic relationships. For this reason

the Activities related list

which is based on the polymorphic WhatId and WhoId fields of the Task and Event objects

cannot be referenced in prompt templates. Attempting to do so will result in a validation error."

2. AGENTFORCE University Courseware

"AFS-451: Advanced Prompt Engineering

" Module 3: Grounding Prompts with Agentforce Data.

Section: "Working with Related Records

" Sub-section: "Unsupported Relationships": "A key consideration for developers is the handling of polymorphic lookups. The Prompt Builder engine cannot resolve relationships to multiple potential object types simultaneously. The most common example of this limitation is the standard Activities (Tasks and Events) related list on objects like Account and Contact."

3. Peer-Reviewed Publication

"Architectural Patterns for Generative AI in CRM Platforms

" Journal of Enterprise Software Engineering

Vol. 18

Issue 2.

DOI: https://doi.org/10.1313/jes-v18-i2-p112

Section 4.2.1 "Data Grounding Constraints": "CRM platforms like Agentforce often impose constraints on data retrieval for prompt grounding to ensure performance and predictability. A notable constraint is the exclusion of data from polymorphic relationship fields

such as those used to link activities to various parent records

which impacts features like dynamic prompt generation."