Examkin

Question

Difficulty: MediumStandard/Custom Report Types and Formats

A Salesforce Administrator is configuring a Custom Report Type to analyze relationships between Accounts (Primary Object) and Partner Surveys (Secondary Custom Object). The management team wants full flexibility to traverse lookup relationships for field selection and ensure accurate record inclusion based on survey responses. Which TWO configuration capabilities or constraints apply when defining the object relationships and field layout for this Custom Report Type? (Select TWO answers)

  1. Fields from objects up to four levels away linked via lookup relationships can be explicitly added to the report layout using the 'Add fields related via lookup' feature.Answer
  2. Configuring the object relationship as 'Each record must have at least one related record' (with relationship) excludes parent Account records that have no associated Partner Surveys from appearing in reports.Answer
  3. C
    Summary report format must be selected during Custom Report Type creation to evaluate row-level record calculations instead of summary formulas.
  4. D
    Defining a custom report type between Accounts and Partner Surveys automatically creates system roll-up summary fields on the Account object across lookup relationships.
  5. E
    Removing a field from the Custom Report Type layout grid restricts Field-Level Security and API read access for users assigned to standard profiles.

Answer

The two correct statements are that fields up to four levels away via lookup relationships can be added to the layout using 'Add fields related via lookup', and that choosing the 'with' relationship ('Each record must have at least one related record') excludes parent records without matching child records.
Custom Report Types allow administrators to traverse up to four levels of lookup relationships to pull related object fields directly into the report layout using the 'Add fields related via lookup' feature. Additionally, setting the object relationship to 'Each record must have at least one related record' creates an inner join, requiring parent records to have corresponding child records to be displayed in reports.

Step-by-Step Solution

1
Evaluate object relationship join behavior
Selecting 'Each record must have at least one related record' acts as an inner join, filtering out Accounts that lack associated Partner Survey records.
Custom report types offer inner join ('with') and outer join ('with or without') options controlling record visibility.
2
Evaluate lookup field expansion capabilities
Administrators can click 'Add fields related via lookup' in the layout editor to reference fields up to 4 levels away from the primary/secondary objects.
This allows reports built on the custom report type to display referenced lookup object fields without creating redundant formula fields.

Key Concept

Custom Report Type Object Relationships and Layout Field Customization
Rate this question

Topics

Standard/Custom Report Types and Formats

More questions from this topic