Force.com Platform Fundamentals

Preface
Introducing the Force.com Platform
About the Sample Recruiting App
Reviewing Database Concepts
Building a Simple App
Enhancing the Simple App with Advanced Fields, Data Validation, and Page Layouts
Expanding the Simple App Using Relationships
Securing and Sharing Data
Collaborating with Chatter
Using Custom Workflow and Approval Processes
Analyzing Data with Reports and Dashboards
Introducing Reports
Report Formats
Setting Up the Recruiting App for Reports
Creating a Summary Report
Try It Out: Create a Summary Report
Try It Out: Add Columns and Filters
Try It Out: Add a Pie Chart
Creating a Matrix Report
Introducing Dashboards
Introducing Custom Report Types
Look At What We've Done
Moving Beyond Point-and-Click App Development
Learning More
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Try It Out: Create a Summary Report

To create our summary report, we'll start by opening the report builder, a powerful visual editor for reports.

  1. On the Reports tab, click New Report.

The first step in creating a report is choosing the right report type. A report type defines the set of records and fields available to a report based on the relationships between a primary object and its related objects. Reports display only records that meet the criteria defined in the report type. Your administrators may have set up custom report types for you, or you can select from the available standard report types.

To help with navigation in this screen, all objects and relationships are grouped in categories like Accounts & Contacts or Customer Support Reports. The custom objects and relationships that we built for our Recruiting app can be found in Other Reports.

The Other Reports category contains all reports based on custom objects. If you've built a custom object that's related to a standard object, such as Account or Contact, you'll also be able to report on your custom object in the standard object's category.

Note

  1. From the Create New Report page, select the Other Reports category.
The Other Reports Category in the Create New Report Page Other reports

Objects that have a many-to-one relationship with another object, like Job Applications and Positions, can either be selected on their own or in the context of their relationship with the other object. For example, if we select Job Applications with Position, our report will count job application records, but can filter, group, or display fields from the related position records as well. This will come in handy a little later when we build reports that count job application records. But because we need to count position records in our report and positions aren't on the many side of a relationship, we'll stick with a standalone positions report for now.

  1. Select Positions.
  2. Click Create.
Custom Report in Report Builder The report builder interface.

Now that we've chosen the report type, we can customize the report. Note that we can't go back and change the report type. To do that, you have to start with a whole new report. The report builder's Preview pane displays a limited set of data; we can also run the report at any time to see if we have the results we're looking for. For example, let's see what a baseline positions report looks like without any customizations.

  1. Click Run Report.
A Positions Report with No Customizations Positions report with no customizations.

The Show drop-down list defaults to My Positions. If you are logged in as a user who does not own any positions, select All Positions before you click Run Report. The report will then display all the positions to which you have access.

Note

As you can see, without specifying any details, we already have a list of position records with a Grand Total at the bottom. This is the equivalent of what we might see if we were creating a tabular report without additional columns. Now let's take this basic report to the next level.

  1. Click Customize to return to the report builder.

When creating a new report, we first need to choose the format of the report that we want to create. The default is tabular. Because we want to group rows of open positions by functional area, we'll create a summary report.

  1. Click Tabular Format and select Summary to change the format.

Now we want to group our rows of data by the Functional Area field.

  1. Find Functional Area in the Fields pane and drag it to the grouping drop zone in the Preview pane. When you have lots of fields, using Quick Find is usually fastest.
Adding a Grouping for a Report Report Builder filter pane and preview for creating a grouping

Say we want to see positions also grouped by region. While the Location field gives us city and state, we want to group data geographically by regions, like USA, UK, and Asia Pacific. By categorizing the location field into buckets, we get a field that can be used for the grouping.

  1. Drag Location from the Field pane into the preview after Position Title.
  2. Click Menu drop-down on Location, and select Bucket this Field.
  3. Type Region in the Bucket Field Name.
  4. Click New Bucket, type USA, and press Enter.
  5. Select:
    • San Francisco, CA
    • Austin, TX
    • Boulder, CO
    • New York, NY
  6. Click Move To, and from its drop-down select USA.
  7. Click New Bucket, type UK, and press Enter.
  8. Move London, England into the UK category.
  9. Move the remaining items into an Asia Pacific bucket.
  10. Click OK.
Creating a Bucket Field Locations bucketed by region
When done, locations are categorized regionally, and you have a bucket field called Region, which appears in the Field pane. However, we don’t need to do anything, because the Platform has automatically added it to the left of Position Title.
Bucket Fields in the Report Preview Region bucket field

We're closer now! Our report still only lists position titles, but now they're grouped by functional areas and by region. Also, each grouping has a record count subtotal in parentheses. These counts will be the basis of the pie chart that we'll add later.