--- title: "Create and validate a metric in Reporting (Beta)" slug: "create-and-validate-a-metric-in-reporting-beta" description: "How do I create a metric from a report in Fullcast Reporting (Beta), and how do I check that it's correct?" tags: ["create a metric", "use reporting", "reports (beta)", "Metric Settings", "Tenant Admin", "revops admin", "reporting beta", "Metrics", "convert to metric", "validate metric"] status: "update" updated: 2026-11-14T20:27:39Z published: 2026-11-14T20:27:39Z canonical: "support.fullcast.com/create-and-validate-a-metric-in-reporting-beta" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fullcast.com/llms.txt > Use this file to discover all available pages before exploring further. # Create and validate a metric in Reporting (Beta) > [!NOTE] > Early access feature > > This feature is currently available for early access. Contact your CSM for more information. A metric is a number your whole team reports on the same way, such as open pipeline or closed-won amount. In Reporting (Beta), you build a metric from a report: build the report, check the number, then convert it. The metric becomes the shared definition everywhere it's used, so check it before you share it. ## Before you begin - Reporting (Beta) must be turned on for your tenant. Refer to [Get started with Reporting (Beta)](/plan-and-pay/docs/get-started-with-reporting-beta). - You need administrator access. Creating and editing metrics is an admin task. - Write your definition down in one sentence first, for example: "Sum of opportunity amount, open opportunities only." ## Build the source report Build and run a report that totals the number you want. For the steps, refer to [Build and save a report in Reporting (Beta)](/plan-and-pay/docs/build-and-save-a-report-in-reporting-beta). - Put the number on the **METRICS** shelf, such as **Amount · sum**. - Add the filters that belong to the definition, such as open opportunities only. - The dataset's starting point decides which hierarchy the metric belongs to: territories, teams, or product groups. ## Check the number before you convert Check the report now, while it's easy to change. Metrics don't keep a version history, so a fix later changes the number everywhere the metric is used. 1. Run the report at the top of your hierarchy and compare the total to a number you already trust, such as a Salesforce report for the same records. 2. Add a territory field to **VIEW BY** and run it again. Check that no single territory looks wrong. 3. From **REPORT TYPE**, select **Detail rows** and confirm the records behind the number are the ones you expect. > [!NOTE] > Note > > - Records with a blank date, records in an Unassigned territory, and records in another currency are where definitions usually go wrong. ## Convert the report to a metric 1. Open the report, and from the **⋮** menu, select **Convert to metric…**. 2. If the report has more than one number, select the one this metric should represent. The open report doesn't change. 3. In **Metric name**, type a name your team will recognize in a list. 4. **Optional:** Enter a **Prefix**, such as `$`, or a **Suffix**, such as `%`. 5. **Optional:** Select **This is a currency amount (responds to currency conversion)** for money values. 6. Click **Create metric**. A metric is one value: the report total. If the report has **VIEW BY** groupings, the dialog tells you they don't carry into the metric. Chips at the top of the dialog show what you're creating, such as **Scalar metric (all-time)** and **Added to Segments**. Each metric name must be unique within its hierarchy. ## Validate the saved metric Run two checks after you save: one confirms the metric compiles, and one confirms its numbers. ### Check that the metric compiles 1. Click the **Settings** gear, and then click **Metrics**. 2. Select the tab for the metric's hierarchy: **Segments**, **Teams**, or **Products**. 3. Find your metric and click the status icon at the start of its row. 4. Click **Validate Now**. When the definition is good, **Definition Check** shows **Ok — the definition compiles.** The check compiles the definition without running it against your data, so it's quick and safe to run any time. To confirm the filters you meant are in the metric, click the arrow on the metric's row. The **Definition** panel shows its **Measure**, **Data**, **Filters**, and **Format**. ### Check that the numbers match 1. Create a new report from the same starting point. 2. In **ENTITIES & FIELDS**, expand **Metrics** and add your new metric to **METRICS**. 3. Add the source report's measure next to it. 4. Add a territory field to **VIEW BY** and click **Run**. The two columns should match on every row. If they don't, compare the metric's **Definition** panel with your source report's filters. ### Optional: Check the metric from your AI client If you use the Fullcast MCP connector, ask your AI client to run the metric at the top of your hierarchy and compare it to your source report. For example: "Run the [metric name] metric at the top of my territory hierarchy." For more, refer to [Use Reporting (Beta) through the Fullcast MCP](/plan-and-pay/docs/use-reporting-beta-through-the-fullcast-mcp). ## Where your metric shows up - The **Metrics** group in **ENTITIES & FIELDS** in the report builder, where you can add it to a report or pin it to a dashboard. - **Settings** > **Metrics**, on the tab for its hierarchy. - Your AI client, through the Fullcast MCP connector. To rename, edit, or delete a metric, refer to [Manage metrics in Reporting (Beta)](/plan-and-pay/docs/manage-metrics-in-reporting-beta). ## Related - [Get started with Reporting (Beta)](/get-started-with-reporting-beta.md) - [Build and save a report in Reporting (Beta)](/build-and-save-a-report-in-reporting-beta.md) - [Manage metrics in Reporting (Beta)](/manage-metrics-in-reporting-beta.md) - [Use Reporting (Beta) through the Fullcast MCP](/use-reporting-beta-through-the-fullcast-mcp.md)