The administrator at Clod Kicks updated the custom object Event to include a lookup field to the primary contact for the event. When running an event report, They want to reference fields from the…

Question

Options

• AConfigure formula fields on event to populate contact information
• BEdit the custom Event report type and add fields related via lookup.
• CCreate a new report type with event as the primary object and Contact as a related object.
• DUse a dashboard with filters to show Event and Contact data as requested.

• A
  4% (1)
• B
  92% (22)
• C
  4% (1)

Explanation

B is correct because when a custom object already has a lookup field to another object, you can edit the existing custom report type to expose fields from the related object - Salesforce lets you add columns from related objects directly in the report type's field layout, no rebuild required.

Why the others are wrong:

• A - Formula fields can surface some contact data, but they're static, limited in scope, and require maintenance for every field you want; it's the wrong tool for general reporting access.
• C - Creating a new report type is unnecessary work when the existing Event report type can simply be edited to include the lookup relationship that already exists.
• D - Dashboards visualize report data; they don't add field access that isn't already in the underlying report type. This doesn't solve the root problem.

Memory tip: Think "edit before rebuild" - if the object already has the lookup, Salesforce lets you extend the existing report type by adding related fields via the lookup, rather than starting from scratch.

No community discussion yet for this question.