The administrator at Cloud 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…

While creating a new report type with Event as primary and Contact as related is a valid approach, if a 'custom Event report type' already exists, editing it directly is more efficient than creating a brand new one.

Dashboards visualize data from reports but do not determine which fields are available in the underlying reports; the report type defines field availability.

Configuring formula fields on Event to pull contact information is technically possible but is inefficient and creates redundant fields if many Contact fields are needed, making report type modification the standard and more scalable solution.

When a custom object (Event) has a lookup field to another object (Contact), the administrator can modify the existing custom report type for the Event object. By adding the Contact object as a related object via the lookup field in the report type definition, fields from the associated Contact record become available for selection and display in reports based on that custom report type.