Get started with Reporting (Beta)

Reporting (Beta) is the new Fullcast reporting experience: you start from the data, then choose how to show it. This article gives you the mental model and the order to build in, with a link for each step.

Turn on Reporting (Beta)

Reporting (Beta) is off by default. A Tenant Admin turns it on for the whole tenant:

1. Click the Settings gear in the top navigation.

2. Click Application Settings.

3. Under Reporting, turn on Enable Reporting (Beta).

Once it's on, a Reports item with a BETA badge appears in the top navigation, next to the classic Reports item. Your classic reports and dashboards keep working, and Reporting (Beta) doesn't change or move them.

How Reporting (Beta) thinks about data

Picture every report as a spreadsheet you build in two steps.

1. Start with what you're counting. Opportunities, accounts, people, or territories. That answer decides everything else.

2. Build the dataset: your spreadsheet. Pick what one row stands for, then add related data. A related list, such as the opportunities on each account, makes the rows more detailed. A linked record, such as an account's owner, adds columns without adding rows. A badge such as Each row = 1 opportunity always tells you what a row is.

3. Decide which rows exist. Choose with, with or without, or WITHOUT for each join, and add filters. These shape every report built on the dataset.

4. Build the report: the summary of your spreadsheet. Choose the numbers to total, how to group them, and how to show them. The report type is a display choice you can change at any time.

5. Save the numbers you trust as metrics. A total in a report is like the sum at the bottom of a spreadsheet column. Converting it to a metric saves that definition so everyone uses the same one.

How Reporting (Beta) differs from classic reports

Classic reports start with a report type, such as a Basic Chart or a Coverage Report, and the type decides what data you can use. Reporting (Beta) flips that order.

Build your reporting, step by step

1. Build a dataset. Choose what each row is, add related data, and filter it. Refer to Build a dataset in Reporting (Beta).

2. Add calculated fields for values your data doesn't store. Refer to Add calculated fields and measures in Reporting (Beta).

3. Set up drill-downs so people can zoom from a total into the detail. Refer to Set up drill-downs in Reporting (Beta).

4. Build, run, and save the report. Refer to Build and save a report in Reporting (Beta). To see whole reports built start to finish, refer to Example: Find coverage gaps in Reporting (Beta), Example: Compare territory balance in Reporting (Beta), and Example: Report on commissions earned in Reporting (Beta).

5. Convert trusted totals to metrics, pin reports to dashboards, and share them, all from the report's ⋮ menu. To turn a total into a metric, refer to Create and validate a metric in Reporting (Beta). To change or delete one, refer to Manage metrics in Reporting (Beta). To work with dashboards, refer to Use a dashboard in Reporting (Beta) and Edit a dashboard in Reporting (Beta). To give people access, refer to Share reports, dashboards, and folders in Reporting (Beta).

6. If something looks off, refer to Troubleshoot Reporting (Beta). If someone can't open or change something, refer to Reporting (Beta) permissions.

Key terms

• Dataset: the data a report reads. It starts from a hierarchy (Territories, Teams, Product groups) or a record type (Accounts, People, Products), plus any related data you add.

• Row: what one line of the dataset stands for, shown in the Each row = badge.

• Related list: related data where each record can have several, such as opportunities on an account. It makes rows more detailed.

• Linked record: related data with one match per record, such as an account's owner. It adds fields, not rows.

• Metrics shelf vs. saved metric: the METRICS shelf in the report builder holds any number you total. It becomes a saved, reusable metric only when you use Convert to metric….

• View by: the fields a report groups by, up to three.

• Calculated field / calculated measure: a formula you write. A calculated field works on each row. A calculated measure works on the report's totals.

• Drill-down: a path people can click through in a report, such as fiscal year, then quarter, then month.

How security works in Reporting (Beta)

Every dataset is secured by a hierarchy, and the starting points say which one, such as Secured by Territories. A report includes only the parts of that hierarchy you have access to, so two people can open the same report and see different numbers. Users and Audit Logs are marked Administrators only. Tenant Admins and Reporting users see every node.

Use Reporting (Beta) from your AI client

With the Fullcast MCP (Model Context Protocol) connector, your AI client can work with Reporting (Beta) too. Reports you save in the app show up there, and what your AI client can do depends on your tenant and your role. For details, refer to Use Reporting (Beta) through the Fullcast MCP.