Section 2 · Salesforce Fundamentals · 18% of exam
2.3 Design Reports, Report Types, and Dashboards
Exam objective
Identify Salesforce capabilities for creating reports, report types, and dashboards that satisfy business questions while respecting access and data structure.
A report answers a question about records that the running user can access. Report formats include tabular, summary, matrix, and joined reports, each suited to different comparisons and groupings. Filters define the population; groupings organize it; formulas and summaries derive measures. A report type determines the primary object and related objects or fields available to the report. Standard report types cover common relationships, while custom report types can expose a carefully chosen set of related records.
Choose the report type from the question’s data shape. If users need accounts with their contacts, the report type must make that relationship available. A report type can include records with or without related records depending on its configuration. That choice changes which rows appear and can silently exclude records. Build a small test report and compare its result with known records before adding charts or dashboards. A report cannot show a field that is unavailable through the chosen report type or inaccessible to the user.
Dashboards present report results as components such as charts, tables, and metrics. Each component uses a source report. A dynamic dashboard runs using the logged-in user’s access; a dashboard with a specified running user reflects that user’s data visibility. The dashboard’s display context is a security decision as well as a presentation choice. A dashboard may show summarized data from records the viewer could not otherwise open when it runs under another user. Use a suitable running user and avoid exposing sensitive aggregates to a broad audience.
Design for an explicit decision. Confirm the audience, refresh expectations, filters, and whether users need drill-down. Keep labels meaningful and avoid overloaded dashboards with metrics that lack definitions. Report subscriptions, folders, and access settings affect whether users can find and receive the information. Salesforce reporting has limits in supported combinations and row visibility; consult current Help for specific limits rather than assuming a report can reproduce every database query.
Applied scenario: A sales director wants a weekly view of open opportunities by stage and region, with expected amount and a trend chart. Use an Opportunities report, filter to open records and the relevant period, group by region and stage, and summarize amount. Validate that the date field matches the business meaning of “weekly.” Add the chart to a dashboard component and choose whether the director’s access should determine the displayed population. If managers should see only their own teams’ records, use a dynamic dashboard or another correctly scoped running-user design. Test the dashboard as a manager and as a representative seller.
Design and risk review: Do not treat a dashboard as a data entitlement mechanism. A fixed running user can reveal summaries beyond a viewer’s direct record access. A custom report type that requires related records can omit otherwise valid parent records. Confusing a report filter with security is another error: filters narrow a report but do not replace access controls. When metrics disagree, inspect the report type, filters, date field, grouping, formula, and running user in that order. Salesforce Certified Platform App Builder | SU ·26 guide alignment 6 Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.
Key takeaways
- Identify Salesforce capabilities for creating reports, report types, and dashboards that satisfy business questions while respecting access and data structure
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards Salesforce Certified Platform App Builder
- SU ·26 guide alignment 7
