Apex Developer Guide

Apex Developer Guide
Release Notes
Getting Started with Apex
Writing Apex
Running Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Apex Cursors
Approval Processing
Authentication
Chatter Answers and Ideas
Use Cases for the CommercePayments Namespace
Connect in Apex
Moderate Chatter Private Messages with Triggers
Data 360 In Apex
DataWeave in Apex
Moderate Feed Items with Triggers
Experience Cloud Sites
Email
External Services
Flows
Formula Evaluation in Apex
Metadata
Permission Set Groups
Platform Cache
Salesforce Knowledge
Salesforce Files
Salesforce Connect
Salesforce Reports and Dashboards API via Apex
Requirements and Limitations
Run Reports
List Asynchronous Runs of a Report
Get Report Metadata
Get Report Data
Filter Reports
Decode the Fact Map
Test Reports
Salesforce Sites
Support Classes
Territory Management 2.0
Integration and Apex Utilities
Debugging, Testing, and Deploying Apex
Apex Reference
Appendices
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Decode the Fact Map

The fact map contains the summary and record-level data values for a report.

Depending on how you run a report, the fact map in the report results can contain values for only summary or both summary and detailed data. The fact map values are expressed as keys, which you can programmatically use to visualize the report data. Fact map keys provide an index into each section of a fact map, from which you can access summary and detailed data.

The pattern for the fact map keys varies by report format as shown in this table.

Report format Fact map key pattern
Tabular

T!T: The grand total of a report. Both record data values and the grand total are represented by this key.
Summary

<First level row grouping_second level row grouping_third level row grouping>!T: T refers to the row grand total.
Matrix

<First level row grouping_second level row grouping>!<First level column grouping_second level column grouping>.

Each item in a row or column grouping is numbered starting with 0. Here are some examples of fact map keys:

Fact Map Key Description
0!T The first item in the first-level grouping.
1!T The second item in the first-level grouping.
0_0!T The first item in the first-level grouping and the first item in the second-level grouping.
0_1!T The first item in the first-level grouping and the second item in the second-level grouping.

Let’s look at examples of how fact map keys represent data as it appears in a Salesforce tabular, summary, or matrix report.

Tabular Report Fact Map

Here’s an example of an opportunities report in tabular format. Since tabular reports don’t have groupings, all of the record level data and summaries are expressed by the T!T key, which refers to the grand total.

Tabular Report Fact Map Keys

Summary Report Fact Map

This example shows how the values in a summary report are represented in the fact map.

Summary Report Fact Map Keys
Fact Map Key Description
0!T Summary for the value of opportunities in the Prospecting stage.
1_0!T Summary of the probabilities for the Manufacturing opportunities in the Needs Analysis stage.

Matrix Report Fact Map

Here’s an example of some fact map keys for data in a matrix opportunities report with a couple of row and column groupings.

Matrix Fact Map Keys
Fact Map Key Description
0!0 Total opportunity amount in the Prospecting stage in Q4 2010.
0_0!0_0 Total opportunity amount in the Prospecting stage in the Manufacturing sector in October 2010.
2_1!1_1 Total value of opportunities in the Value Proposition stage in the Technology sector in February 2011.
T!T Grand total summary for the report.