EXPERIENCE-CLOUD-CONSULTANT practice question 14 of 25

Ursa Major Solar would like to use three Record Detail components on a page to display object details for the Account, Case, and Opportunity objects for the user who is logged in to the company’s portal. When they drop the components on the page, they are not getting the desired results. What is causing this issue?

Full set: 185 questions
Answer options
A: The Record Detail component populates the recordID associated with the object for the page template, so this component will not work for this use case. Correct answer
B: The Record Detail component populates the record associated with the object for the page template so this component will only work on the Home page template
C: The Record Detail component is a custom component and was not configured correctly
D: The Record Detail component will only show record details for the Case object.
Correct Answer:
A. The Record Detail component populates the recordID associated with the object for the page template, so this component will not work for this use case.
Explanation

The Record Detail component can show only the record whose recordId is passed in the page’s URL. Experience Builder assigns a single recordId based on the object the page is associated with, so multiple Record Detail components for different objects cannot simultaneously obtain the required recordId on one page.

Why Incorrect

B. Works on any object-specific page, not limited to Home pages.
C. Record Detail is a standard component; no custom mis-configuration involved.
D. Component is object-agnostic; it isn’t restricted to Cases.

References

1. Salesforce Help, “Record Detail Component” – Behavior paragraph: “Displays the fields on the record identified by the page’s recordId parameter.” (help.salesforce.com, Summer ’23)

2. Salesforce Experience Cloud Site Developer Guide, “Create Object Pages,” p.134: “Each object page supplies one recordId, therefore only one record’s details can be rendered per page.”

Scroll to Top