Fast Salesforce Product Forecasting with the New Pivot View

Written by

Peter Gascoyne

November 20, 2026

Pivot view for Salesforce product forecasting by month, Grids 6.82 by RavenApps

Grids 6.82 adds a Pivot view: records down the side, months across the top, editable values in the cells. Product forecasting becomes one screen in Salesforce instead of a spreadsheet round trip.

Summary

Grids 6.82 adds a Pivot view, which turns any grid in Salesforce into a time-based view: records down the side, months across the top, values you can edit in the cells. The first use case is Opportunity Product Schedules, so product forecasting becomes one screen instead of a spreadsheet.

‍

Edit any month, see row, monthly and overall totals update as you type, keep the leading columns frozen while you scroll, and save every change in one go. One click switches between Table and Pivot. Available in Grids 6.82.

‍

Editing an Opportunity Product Schedule forecast month by month in the Grids Pivot view, with row and column totals updating live
Editing a product forecast month by month on an Opportunity, with totals recalculating as the values change.

‍

Why did we build this?

Product forecasting in Salesforce is a data model problem that became an interface problem.

‍

Opportunity Product Schedules are a perfectly good structure: a row per product per period, with quantity and revenue. The trouble is that they are stored the way a database wants them and read the way a database wants them, one record at a time, down a list. Nobody forecasts like that. People forecast across months.

‍

So the schedule gets exported to a spreadsheet, laid out as a grid of months, worked on, and typed back in. Or more often, it never goes back in at all, and the forecast lives in the spreadsheet while Salesforce holds a number nobody trusts.

‍

Pivot gives the schedule the shape people already think in, inside Salesforce, editable.

‍

What is the Pivot view?

Pivot takes a grid and transposes part of it against time. You choose what forms the rows, which date field spreads across the columns, and which values appear in the cells.

‍

For Opportunity Product Schedules that means products down the left, months across the top, and quantity and revenue in each cell. The same mechanism works for anything with a record, a date and a number: timesheets, delivery plans, subscription schedules, recognised revenue.

‍

Edit any month, save once

Cells are editable. Change a quantity in March, a revenue figure in June, a handful more across the year, and save them all in a single action. The grid tracks unsaved changes and tells you how many are pending, so a long forecasting session does not end in uncertainty about what was actually written.

‍

This is the whole point of the feature. A read-only pivot is a report, and Salesforce already has reports.

‍

Totals that update as you type

Row totals, monthly column totals and an overall total recalculate live as values change. You see what moving a product's delivery from Q1 to Q2 does to the quarter before you commit it.

‍

Totals can sit at the start or the end of the grid, which sounds like a preference and turns out to matter: the number people check most should be the one they do not have to scroll to.

‍

Frozen leading columns

Scrolling across twelve or twenty-four months is only useful if you can still see which product you are looking at. The leading columns stay frozen while the months scroll, and how many are frozen is configurable.

‍

One click between Table and Pivot

Pivot is a view on the grid rather than a separate component. A toggle in the toolbar switches between the table and the pivot on the same data, and a grid can be set to open in Pivot by default.

‍

That matters for adoption. Teams who want the month view get it immediately, and anyone who needs the record-level detail is one click away rather than in a different app.

‍

Quantity, revenue, or both

Schedules in Salesforce can be quantity, revenue or both, and Pivot follows the schedule type on the record rather than making you pick globally. Where a product is scheduled for both, both appear, each with its own column under the month and its own totals.

‍

How is this different from a report or a spreadsheet?

  • Against a matrix report: a report can lay schedules out by month, and it is read-only. Pivot is editable, so the review and the update are the same action.
  • Against a spreadsheet: the spreadsheet is editable and outside Salesforce, which means a round trip, a version question, and a forecast that drifts. Pivot keeps it on the record.
  • Against the standard schedule editor: the standard interface edits one product's schedule at a time. Pivot shows every product on the opportunity at once.
  • Against a custom build: a bespoke Lightning component does this too, for a development budget and a maintenance commitment. Pivot is configuration.

‍

Where it fits beyond opportunity products

Product schedules are the first case rather than the only one. The pattern applies anywhere a record carries values spread over periods:

  • CPQ and Revenue Cloud: scheduled quantities and amounts against contracted products
  • Timesheets: people down the side, days or weeks across, hours in the cells
  • Delivery and capacity planning: units per month against a plan
  • Budget and spend tracking: planned against actual, period by period

‍

If you are running one of these, we would like to hear about it. The configuration for a new use case is a block of JSON rather than a project, and the shape of the second and third cases is what decides where this goes next.

‍

What it is not for

Pivot is a view over a grid, so it inherits the grid's scope. It is not an analytics engine: cross-object aggregation across the whole org is still a report or a dashboard. And it is not a planning tool with its own storage. Every value you edit is a Salesforce record, which is the point, but it does mean the structure has to exist before you can pivot it.

‍

How to get started

  1. Install or upgrade via the AgentExchange listing or the Package Version page.
  2. Add Pivot to the Action picklist on the Grid object, under Setup, Object Manager, Grid.
  3. Add it to the Action field on each grid that should offer it.
  4. Configure the pivot on the grid: the row key and label, the date field, the value fields, totals position and how many columns to freeze.
  5. Open the grid, switch to Pivot, and edit a month.

‍

Existing grids are unaffected until you add the action. Grids is free in sandboxes, with full features and no time limit, so you can point Pivot at your own schedules before deciding anything.

‍

Useful Links

‍

Thank You

Thanks for reading. If you forecast products, hours or spend by period and want to see what Pivot looks like over your own data, bring the use case to a call and we will configure it live. Book a Call or Contact Us.

In this article:
Boost Salesforce Productivity with Grids & DocGen

40+ features to power up your workflows

Discover Grids
Discover DocGen
"A must have tool for efficient data management"

Alex Andony, Truly Investor Capital

AppExchange

Start working smarter in Salesforce