Soru

Zorluk: OrtaStandard/Custom Report Types and Formats

A System Administrator is configuring a Custom Report Type to support cross-departmental reporting between Accounts, Opportunities, and custom Delivery Schedules. Which TWO configurations or behaviors accurately describe Salesforce Custom Report Types?

  1. Selecting 'Each record may or may not have related records' (with or without relationship) ensures parent records display in reports even if they have no related child records.Cevap
  2. B
    Row-level calculation rules must be built as Summary Formulas directly within the Custom Report Type field layout editor before users can run reports.
  3. Administrators can add fields from objects related via lookup (up to four levels reference chain) to the Custom Report Type layout so users can include them in reports.Cevap
  4. D
    Choosing the 'with or without' relationship automatically bypasses Organization-Wide Defaults (OWD) so all users can view underlying child records regardless of sharing rules.
  5. E
    Custom Report Types require a Master-Detail relationship between objects and cannot link objects joined solely by Lookup relationships.

Cevap

The correct configurations are: choosing 'Each record may or may not have related records' ensures parent records appear without child records, and administrators can add fields from related objects via lookup up to four levels deep into the Custom Report Type layout.
Selecting the 'with or without' option configures an outer join so that parent records display regardless of child record presence. Additionally, administrators can use the 'Add fields related via lookup' feature within the Custom Report Type layout editor to reference fields up to four lookup levels away.

Adım Adım Çözüm

1
Analyze object relationship join options in Custom Report Types
Using the 'with or without' relationship acts as an outer join, allowing parent records to be displayed in reports even when related child records are missing.
Business reporting often requires identifying parent records (e.g., Accounts) that lack activity or child records (e.g., Opportunities).
2
Evaluate layout customization capability for referencing lookup objects
Administrators can click 'Add fields related via lookup' in the report layout editor to traverse up to 4 levels of lookup relationships.
This avoids creating redundant custom formula fields solely for reporting purposes.
3
Verify security enforcement and distractor statements
Salesforce security (OWD, sharing rules, profiles) is always strictly enforced in reports, and Custom Report Types support lookup relationships.
Report visibility never overrides underlying record-level security.

Anahtar Kavram

Custom Report Type Object Relationships and Layout Customization
Bu soruyu puanla