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?
- 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
- BRow-level calculation rules must be built as Summary Formulas directly within the Custom Report Type field layout editor before users can run reports.
- 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
- DChoosing the 'with or without' relationship automatically bypasses Organization-Wide Defaults (OWD) so all users can view underlying child records regardless of sharing rules.
- ECustom 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
Anahtar Kavram
Custom Report Type Object Relationships and Layout Customization