Lesson 12 of 22 · All lessons

Section 5 · Reporting · 15% of exam

5.2 Dashboards, Components, and Data Context

2 min read Updated Nov 19, 2026

Exam objective

Build trustworthy reports by validating definitions, access, folder sharing, and the results users consume.

Core concepts

Report quality begins with a precise metric definition. “Revenue” may mean closed-won amount, bookings in a period, or recognized revenue from another system. Salesforce report fields do not determine business meaning by themselves. Confirm the object, stage or status conditions, date field, currency assumptions, and treatment of renewals or cancellations before publishing a report. Label the report so users can understand what it includes. Use a validation pass before sharing: inspect filters, review several detail records, compare grouped totals with the source rows, and test with a representative user. If the report uses a cross filter or joined blocks, ensure each block answers the intended question. A summary formula can be useful, but its calculation should be understandable and match the business definition. Avoid relying on a chart alone to verify numbers.

Report folders help organize and share analytics assets. Folder access can let users view or manage reports and dashboards, but it does not grant access to all underlying records. A user might open a report and see fewer rows than an administrator because record visibility differs. Likewise, a user with data access might not see a report if the folder is not shared with them. Diagnose these layers separately.

Scenario: A regional supervisor cannot see a report in the analytics folder. First confirm the report exists and that the supervisor has access to the folder. If the report opens but appears empty, review report filters and the supervisor’s record access. If the report is visible but a field is missing, check the report type and field permissions. This structured diagnosis avoids broadly granting access to solve a folder-navigation issue.

Subscriptions or scheduled delivery, where enabled and permitted, can send report results or notifications. Before scheduling, check recipients, folder and data access, and organizational policy. A scheduled email can carry sensitive information outside the interactive Salesforce session. Use only approved recipients and delivery practices.

Never assume that folder sharing makes a report’s data safe for every recipient. Test with the intended audience and follow company policy for exports and email delivery.

Troubleshoot in order: asset access, report definition, field availability, record visibility, then refresh or scheduling behavior.

Extra concept

Extra concept: Consistent report naming conventions can include the business subject, audience, and time scope. This reduces duplicate reports and helps users find an authoritative version.

Key takeaways

  • Report quality begins with a precise metric definition.
  • Use a validation pass before sharing: inspect filters, review several detail records, compare grouped totals with the source rows, and test with a representative user.
  • Report folders help organize and share analytics assets.
  • Official references: https://help.salesforce.com/s/articleView?id=analytics.analytics_overview.htm&language=en_US https://help.salesforce.com/s/articleView?id=sf.security_overview.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&language=en_US&type=5

Check your knowledge

Answer exam-style Reporting questions with answers and explanations.

Practice Reporting
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Foundations simulator: same number of questions, same time limit.

Get Complete Access