September 1, 2026

Back to the Basics: Salesforce Reporting, Data Management & Data Quality

Key Takeaways

  • Choose the right Report Type before building a report.
  • Understand the differences between Tabular, Summary, Matrix, and Joined Reports.
  • Know how running users and Dynamic Dashboards affect the information users see.
  • Use Data Import Wizard for simpler imports and Data Loader for larger or more advanced operations.
  • Maintain regular backups and understand your recovery options.
  • Use Matching Rules, Duplicate Rules, and Validation Rules together to maintain data quality.

A Salesforce org is only as valuable as the data and insights it provides. Reports and dashboards help teams turn Salesforce records into actionable information. Data-management tools help administrators import, update, export, and recover information. Data-quality tools help prevent duplicates and incorrect information from entering the system.

As Salesforce environments become larger and more complex, understanding these fundamentals becomes increasingly important. This blog provides a practical refresher on Salesforce reporting, dashboards, data management, backup, and data-quality concepts that administrators regularly encounter.

Salesforce Reports

Reports are one of the primary ways Salesforce users analyze information. While creating a basic report is relatively simple, understanding Report Types and report formats is essential for building useful and reliable reporting solutions.

Report Types

A Report Type determines which objects, relationships, fields, and records are available when creating a report. Salesforce provides standard Report Types, but administrators can also create Custom Report Types when more control is required.

Common configurations include:

  • Primary Object with Related Object
  • Primary Object with or without Related Object
  • Custom combinations of objects and fields

For example, a Custom Report Type can be used when users need to report on Accounts with Opportunities, including Accounts that do not yet have Opportunities. The Report Type effectively determines the data foundation available to the report builder.

Salesforce Report Formats

Salesforce provides four primary report formats.

Tabular Reports

Tabular Reports display records in a straightforward table. They are useful when users simply need a list of records but do not require grouping or complex summaries.

Summary Reports

Summary Reports allow records to be grouped. They are useful for analyzing information by categories such as Account, Owner, Stage, or another field.

Matrix Reports

Matrix Reports allow data to be grouped by both rows and columns. This makes them useful when users need to analyze information across two dimensions.

Joined Reports

Joined Reports combine multiple report blocks into one report. For example, a Joined Report could display Opportunities per Account alongside Cases per Account, allowing users to compare related information in one place.

Salesforce Dashboards

Dashboards turn report data into visual information through components such as charts, tables, gauges, and metrics. They are particularly useful when executives, managers, and operational teams need to monitor key information without opening multiple individual reports.

Running Users

A dashboard has a running user whose security settings determine the data displayed. This is an important concept because users viewing the same dashboard may see information according to the permissions of the configured running user. For example, if a dashboard runs as a particular administrator, the dashboard may display data available to that administrator.

Dynamic Dashboards

Instead of relying on one fixed running user, Dynamic Dashboards display information according to the security access of the user viewing the dashboard. This makes Dynamic Dashboards useful when a single dashboard needs to serve multiple groups with different access levels. Other dashboard considerations include:

  • Dashboards support up to 20 components.
  • Dashboards are stored in folders.
  • Users need access to the dashboard folder and the underlying reports.
  • Dashboard data reflects the most recent refresh.
  • Standard dashboards can be scheduled for refresh.
  • Dynamic Dashboards are refreshed manually by users.

When users drill down into underlying report details, their own Salesforce access still determines which records they can see.

Reports and Dashboard Folders

Reports and dashboards are stored in folders, and folder access controls who can work with them. Folders can be shared with individual users, Roles, or Public Groups. Depending on the configuration, users can receive different levels of access, including:

  • Viewer
  • Editor
  • Manager

This means a user may have access to Salesforce data but still be unable to access a particular report or dashboard because they do not have access to its folder.

Report and Dashboard Subscriptions

Subscriptions allow users or teams to receive report and dashboard updates automatically. Depending on the configuration, updates can be scheduled daily, weekly, or monthly. Some reporting capabilities can also notify users when specific metrics reach defined thresholds. This helps teams monitor important business information without having to manually open reports every day.

Salesforce Data Management

Data management is one of the most important responsibilities of a Salesforce administrator. Organizations constantly need to import new records, update existing information, transfer ownership, remove obsolete data, and export information for analysis or backup. Salesforce provides several tools for these tasks, with the Data Import Wizard and Data Loader being two of the most important.

Data Import Wizard

The Data Import Wizard is a browser-based tool designed for relatively straightforward data operations. It can be used for imports, updates, and upserts and supports datasets of up to 50,000 records. It is useful for common objects such as Accounts, Contacts, and Leads, as well as supported custom objects. For administrators performing smaller, straightforward imports, its browser-based interface makes it a convenient option.

Data Loader

Data Loader is designed for larger and more advanced data operations. It supports up to 5 million records and provides capabilities including:

  • Insert
  • Update
  • Upsert
  • Delete
  • Export
  • Hard Delete
  • Command-line operations
  • SOQL-based exports
  • Large-volume processing

Data Loader can also be used for more advanced and repeatable data-management processes.

Data Import Wizard vs. Data Loader

The choice between the two tools generally comes down to the scale and complexity of the operation.

Capability Data Import Wizard Data Loader
Browser-based interface Yes No
Maximum records 50,000 5,000,000
Deduplication capabilities Yes Limited/manual
Insert Yes Yes
Update Yes Yes
Export No Yes
Delete Limited Yes
Hard Delete No Yes
Command-line support No Yes
Scheduled loads No Yes
Large datasets Limited Yes
SOQL-based export No Yes
Export deleted records No Yes

For a small administrative import, the Data Import Wizard may be sufficient. For large datasets, exports, automation, or advanced data operations, Data Loader is generally the more appropriate tool.

Backup and Restore

Data loss can have significant operational consequences, which makes backup an important part of Salesforce administration. Administrators can use Salesforce’s Data Export Service, Data Loader, reports, or dedicated backup solutions depending on the organization’s requirements.

Data Export Service

The Data Export Service is available through Salesforce Setup. It can be used to generate CSV-based exports of Salesforce data. Key characteristics include:

  • Exports can be initiated immediately.
  • Exports can be scheduled weekly or monthly.
  • Supported object data can be exported.
  • Large exports can be split into multiple files.
  • Salesforce sends an email containing a link to the export.
  • Export files are available for a limited period for download.

Organizations with more demanding recovery requirements may also consider dedicated backup solutions that provide more comprehensive recovery capabilities.

Data Loader Exports

Data Loader can be used to export records from Salesforce and supports more targeted data extraction. Administrators can use SOQL to identify the records and fields they need, making Data Loader useful when a complete org-wide export is unnecessary. Data Loader also provides an “Export All” capability for retrieving records that have been deleted but are still available through Salesforce’s supported recovery mechanisms.

Mass Transfer and Mass Delete

Salesforce also provides administrative tools for managing records in bulk.

Mass Transfer

Mass Transfer allows administrators to transfer ownership of multiple records from one user to another. This can be particularly useful when an employee leaves the organization, changes roles, or when account ownership needs to be reorganized.

Mass Delete

Mass Delete allows administrators to delete multiple records based on defined criteria. It can be useful for removing obsolete, duplicate, or unwanted records. However, administrators should use it carefully because bulk deletion can have downstream effects on related data and business processes.

Recycle Bin

The Recycle Bin provides a safety net for deleted records. Soft-deleted records generally remain available for recovery for up to 15 days, unless they are permanently deleted earlier or removed because of storage limitations. When records are restored, Salesforce can restore applicable relationships as well.

Maintaining Salesforce Data Quality

A Salesforce org can have a sophisticated architecture and strong security controls and still fail if users do not trust the data. Data quality therefore needs to be addressed proactively. Salesforce provides several tools that can help administrators identify duplicates, prevent bad data, and enforce business requirements.

Matching Rules

Matching Rules determine how Salesforce identifies potential duplicate records. They define the criteria Salesforce uses to compare records and can use different matching approaches, including exact and fuzzy matching.

For example, a Matching Rule could identify potential duplicates based on an email address or identify variations in names such as “Robert” and “Bob.” Matching Rules can also support comparisons across certain objects, such as Leads and Contacts. The important thing to remember is that Matching Rules determine how Salesforce identifies a potential match.

Duplicate Rules

Duplicate Rules work together with Matching Rules. While a Matching Rule identifies how records are considered potential matches, the Duplicate Rule determines what Salesforce should do when a match is found. Depending on the configuration, Salesforce can:

  • Alert the user
  • Allow the record to be saved
  • Block the record from being saved

This distinction is important when designing a duplicate-management strategy. For example, an organization might allow users to save a potential duplicate but display a warning, or it might block the save entirely when an exact match is detected.

Validation Rules

Validation Rules enforce business requirements when records are created or updated. A Validation Rule evaluates a formula. If the formula evaluates to TRUE, Salesforce considers the record invalid and prevents it from being saved.

For example, an organization might create a Validation Rule that requires a specific field to be completed when an Opportunity reaches a certain Stage. Another rule might prevent users from entering a discount above an approved threshold. Validation Rules can:

  • Validate data against defined business requirements.
  • Reference related-record information where supported.
  • Display custom error messages.
  • Apply to data entered through many Salesforce interfaces and supported import or API operations.
  • Prevent records from being saved when the defined criteria are not met.

A useful way to remember the difference between the three main data-quality tools is: Matching Rules identify potential duplicates. Duplicate Rules determine what happens when a duplicate is found. Validation Rules enforce business requirements.

Conclusion

Reliable Salesforce reporting starts with reliable Salesforce data. Reports and dashboards help organizations turn data into insights, while Data Import Wizard and Data Loader provide the tools administrators need to move and maintain information at scale.

At the same time, backup and recovery capabilities help protect important information, while Matching Rules, Duplicate Rules, and Validation Rules help maintain data quality. For Salesforce administrators, these are more than individual features. Together, they form the foundation for a Salesforce org that users can trust.

Frequently Asked Questions (FAQs)

  1. What is the difference between Data Import Wizard and Data Loader?
    The Data Import Wizard is a browser-based tool designed for simpler imports of up to 50,000 records. Data Loader supports larger datasets of up to 5 million records and provides more advanced capabilities such as export, delete, hard delete, and command-line operations.
  2. What is a Dynamic Dashboard in Salesforce?
    A Dynamic Dashboard displays data based on the security access of the user viewing it rather than relying on one fixed running user.
  3. What is the difference between a Matching Rule and a Duplicate Rule?
    A Matching Rule determines how Salesforce identifies potential duplicate records. A Duplicate Rule determines what happens when a potential duplicate is identified.
  4. What is a Validation Rule
    A Validation Rule uses a formula to determine whether data meets defined business requirements. If the formula evaluates to TRUE, Salesforce prevents the record from being saved and displays an error message.
  5. How long do deleted Salesforce records remain in the Recycle Bin?
    Deleted records generally remain available for recovery for up to 15 days, subject to Salesforce’s applicable storage and deletion behavior.
Marcelo Albajari
Marcelo Albajari Marcelo Albajari is the Development Services Strategic Consulting Director at IT Convergence, bringing over 30 years of experience in ERP and CRM enterprise applications, automation and cloud integrations. A former Oracle Corporation manager, Marcelo has led technical implementations for over 100 enterprise clients across the US and LATAM, helping organizations navigate complex digital transformations with tailored, high-impact technical solutions.

Related Blogs