Lesson 16 of 23 · All lessons
Salesforce Platform Administrator II
0 of 23 complete
1Exam Overview
  1. 1.1Platform Administrator II Complete Exam Overview
2Security and Access20%
  1. 2.1Sharing architecture: records, fields, and inherited access
  2. 2.2Profiles, permission sets, delegated administration, and
  3. 2.3Person accounts and complex account-contact models
3Objects and Applications19%
  1. 3.1Object relationships, record types, and schema design
  2. 3.2Applications, Lightning App Builder, Dynamic Forms, and
  3. 3.3Record types, page layouts, and related-list experience
4Auditing and Monitoring10%
  1. 4.1Debug logs and Setup Audit Trail
  2. 4.2Sensitive data, sandbox controls, and security review
  3. 4.3Reviewing security changes and pending access updates
5Cloud Applications11%
  1. 5.1Sales lifecycle: products, price books, schedules, orders, and
  2. 5.2Forecasting and Enterprise Territory Management
  3. 5.3Knowledge, entitlements, and service channels
  4. 5.4Salesforce product suite and platform extension choices
6Data and Analytics Management13%
  1. 6.1Data quality, validation, duplicates, enrichment, and archiving
  2. 6.2Complex reports, dashboards, and analytic design
  3. 6.3External data, backup and restore, and import methods
7Environment Management and Deployment
  1. 7.1Sandboxes, packages, and metadata movement options
  2. 7.2Change set composition, validation, and deployment practice
  3. 7.3Sandbox selection, refresh, and data protection
8Process Automation20%
  1. 8.1Choosing Flow, approvals, formulas, and legacy automation
  2. 8.2Order of execution, recursion, and automation interaction
  3. 8.3Automation troubleshooting, testing, and fault handling

Section 6 · Data and Analytics Management · 13% of exam

6.2 Complex reports, dashboards, and analytic design

4 min read Updated Nov 17, 2026

Exam objective

Given a scenario, select appropriate analytic tools: custom report types, snapshots, charts, summary formulas, buckets, joined reports, cross filters, dynamic dashboards, and dashboard filters.

Start a report from the question and the data relationship. A standard report type works when its object relationships include the required records and fields. A custom report type defines which primary object and related objects appear and whether records without related records are included. Carefully choose the relationship option because 'with' versus 'with or without' changes which rows appear. Custom report types can expose fields from related objects and support business-specific report layouts, but they do not grant access to records or fields.

Use summary fields and groupings to answer aggregate questions. Summary formulas calculate values across report groupings, while row-level formulas calculate per record within supported report contexts. Bucketing groups values into categories without changing stored data; it is useful for analysis but should not become the source of an operational classification that other automation depends on. Charts visualize report groupings, and filters should reflect the question's time period, status, and population. Validate totals against known sample records.

Joined reports combine blocks that can use different report types and show related views side by side. They help compare datasets that cannot be represented as one ordinary report, but their structure requires careful grouping and filter alignment. Cross filters answer questions such as accounts with opportunities or cases without activities. A cross filter is useful when the presence or absence of related records matters, rather than when the user needs a detailed joined row for every child record.

Reporting snapshots capture aggregated values at a point in time and store them in a target object. They can support historical trend reporting when the underlying source data changes and the business needs a periodic snapshot. Configure the source report, target object, field mappings, and schedule; then test that each snapshot represents the intended period. Snapshots are not a live mirror and require storage, retention, and ownership planning. They can preserve summary measures but may not retain every source detail.

Dashboards present report data as components. A dynamic dashboard runs as the viewing user, which helps users see data they can access without maintaining many separate dashboards. Dashboard filters let viewers narrow displayed data along configured dimensions. A dashboard running as a specified user can show data based on that user's access, so choose the running user carefully and control folder permissions. Neither filters nor dynamic behavior should be treated as a substitute for record and field security.

When a report seems wrong, check report type, filters, date field, hierarchy, record access, field-level security, and grouping. If expected records are missing, determine whether the report type excludes records without a related object. If a dashboard number differs from a source report, compare running user, filters, currency, and refresh state. Use a stable validation set of records and explain each inclusion or exclusion. Store reports in folders with least-privilege access and govern shared dashboards.

Exam focus: match each tool to its analytical question. Use custom report types to shape available object relationships; cross filters for existence or absence; joined reports to compare blocks; snapshots for historical aggregates; buckets for ad hoc grouping; and dynamic dashboards for viewer-specific results. Check user context and folder access when sensitive data is involved. A report can be technically valid yet analytically misleading if its population or time period is wrong.

Before building a complex report, state the intended row population and denominator. This catches report-type and filter errors earlier than chart formatting does.

Performance and usability also matter. Limit report columns to useful fields, avoid excessive formula complexity, and use filters that allow the query engine to narrow the data set. Give reports meaningful names and descriptions so users understand their scope. Schedule refresh or subscriptions only for appropriate audiences. If a dashboard is used for operational decisions, show the last refresh time and define an owner for report changes. Validate a dashboard on a non-admin account and confirm that its visual summary agrees with the underlying report rows.

Practical scenario

A service director needs a weekly historical count of open cases by priority, even though cases close during the week. Use a scheduled reporting snapshot based on a report with a clearly defined open-case population, map the summary fields into a target object, and test the schedule. Build a dashboard from the snapshot records for trends. A live report alone would show current open cases and lose the historical weekly state.

Extra concept

Analytics context can expose data through subscriptions, exports, and dashboard running users. Review sharing and folder access as part of report design, and test with a non-admin viewer.

Key takeaways

  • Choose report types and filters based on the intended row population.
  • Use snapshots for historical aggregates and cross filters for related-record existence.
  • Review folder access, dashboard context, and report freshness.
  • Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.reports_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.reports_snapshots.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.dashboards_dynamic.htm&type=5

Check your knowledge

Answer exam-style Data and Analytics Management questions with answers and explanations.

Practice Data and Analytics Management
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

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

Get Complete Access