> ## Documentation Index > Fetch the complete documentation index at: https://support.fieldko.com/llms.txt > Use this file to discover all available pages before exploring further. # Trend Reports Over Time > Compare retail execution metrics across weeks, months, and call cycles with relative date filters and date grouping, and know when you need reporting snapshots. Trend reports show whether execution is getting better or worse: call compliance this month compared with last, OSA week by week, or time in store across call cycles. Use this page to turn any report recipe into a trend report, and to find out which metrics need reporting snapshots to show history. ## User Permissions Needed | To do this | You need | | - | - | | Create, edit, and save reports | Create and Customize Reports | | See FieldKo fields and records in reports | FieldKo Manager Permission Set | ## Know Which Metrics Have History Some FieldKo fields record events, and others hold only the current state. You can trend event data directly. Current-state data needs a snapshot. | Metric | Data | Can You Trend It Directly? | | - | - | - | | Call compliance, strike rate, visits per store | Each visit's **Planned Start**, **Actual Start**, and **Status** | Yes. Group visits by date. | | Time in store, attendance | Each visit's **Actual Time Spent (Mins)**; each day's **Attendance** record | Yes | | Orders, pack-outs | Each order's and pack-out's date | Yes | | Survey scores, promotion compliance | Each answer's **Created Date** and each survey's **Completion Date** | Yes | | OSA from all rangings | Each ranging's **Created Date** and line items' **Is Present** | Yes, with the **Rangings With Or Without RangingLineItems** report type | | Coverage from **Last Check-Out** | One date per store, overwritten by each visit | No. Use visits instead, or a snapshot. | | OSA from **Product Availability** or **Is Current Ranging** | Only each store's latest ranging | No. Use all rangings instead, or a snapshot. | | **Next Visit Due**, call cycle and field campaign totals | Recalculated as visits change | No. Use a snapshot. | ## Build a Trend Report Start from any recipe report that's based on event data, and then change the date filter and grouping: 1. Open the report, and then click **Edit**. 2. In **Filters**, set the date field to a relative range, such as **Last 12 Weeks** or **Last 6 Months**. Relative dates move with the calendar, so the report stays current without editing. 3. In **Group Rows**, add the same date field. 4. Click the arrow next to the date grouping, click **Group Date By**, and select **Calendar Week** or **Calendar Month**. 5. Optional: To compare reps side by side, group the rows by **Sales Representative**, and add the date to **Group Columns** instead. This makes a matrix report. 6. Click **Save & Run**. To learn which relative values you can use, see [Relative Date Filter Reference](https://help.salesforce.com/s/articleView?id=sf.filter_dates_relative.htm\&type=5) in Salesforce Help. ### Examples | Trend | Report Type | Date Filter | Group By | | - | - | - | - | | Call compliance by week | **Visits** | **Planned Start**: **Last 12 Weeks**, and less than **Today** | **Planned Start** by **Calendar Week** | | Stores visited each month | **Visits**, with **Status** equals **Completed** | **Actual Start**: **Last 6 Months** | **Actual Start** by **Calendar Month**; summarize **Account** with **Unique** | | OSA by week | **Rangings With Or Without RangingLineItems** | **Created Date**: **Last 12 Weeks** | **Created Date** by **Calendar Week** | | Order value by month | **Accounts with FieldKo Orders with FieldKo Order Line Items** | **Created Date** (FieldKo Order): **Last 12 Months** | **Created Date** by **Calendar Month** | | Time in store by call cycle | **Visits**, with **Status** equals **Completed** | **Actual Start**: **This Year** | **Call Cycle** | The **Visits** report type is the one your admin creates for the recipes. For the formulas, such as **Completed (%)** and **OSA**, use the ones in each recipe: [Call Compliance and Strike Rate](/managers/platform/recipes/call-compliance) and [On-Shelf Availability and Distribution](/managers/platform/recipes/availability). ### Chart Suggestion Use a line chart with the date on the x-axis. For two metrics with different scales, such as visits and compliance percentage, use a line chart with a second axis, or put two charts side by side on a dashboard. ## Compare This Period with the Last * **This month compared with last month:** Filter the date field to greater than or equal to **Last Month**, and group by **Calendar Month**. You get two columns: last month and this month to date. * **Same week, several reps:** Use a matrix with reps as rows and **Calendar Week** as columns, and add conditional formatting so low values show in a warning color. Don't rely on color alone: keep the numbers visible. * **Call cycles:** FieldKo call cycles start on Mondays, but the first day of a **Calendar Week** in reports depends on your locale. To compare whole cycles, group by **Call Cycle**. Salesforce's fiscal filters, such as **This Fiscal Quarter**, use your org's fiscal year settings in Setup. FieldKo uses its own **Fiscal Year Start Month** on the **FieldKo Configuration** tab to build call cycles. If the two differ, group by **Call Cycle** or by calendar periods instead of fiscal periods. ## Get True History with Reporting Snapshots To see how a current-state metric changed, such as the percentage of stores **Past Due** each Monday, or coverage week by week, Salesforce needs to save a copy of the report's results on a schedule. That's a reporting snapshot. Your admin sets it up: a source report, a custom object to hold the results, and a schedule. You then report on the snapshot object like any other data. Ask your admin for a snapshot when you know which report and summary you want to keep, and how often. Snapshots record history only from the day they start, so ask early. See [Dashboard Running Users and Reporting Snapshots](/platform/reports/dashboards-and-snapshots). ## See Also * [Retail Execution Metrics](/managers/platform/retail-metrics) * [Coverage and Visit Frequency](/managers/platform/recipes/coverage) * [Build a Perfect Store Dashboard](/managers/platform/perfect-store-dashboard) * [Dashboard Running Users and Reporting Snapshots](/platform/reports/dashboards-and-snapshots) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.