16 custom report types, 21 reports, 3 dashboards and 6 list views for Salesforce Net Zero Cloud (now sold as Agentforce Net Zero), using core Lightning reporting only. No CRM Analytics, no Einstein, no managed package, no custom objects or fields. API 67.0.
On the name: the product launched as Sustainability Cloud, became Net Zero Cloud in 2022 and
Agentforce Net Zero in 2025. Everything here is labelled NZC: because that is what the
object API names, the Setup menu and the developer guide still say — and because a report
type's API name can't be renamed in place, only deleted and recreated in every org that has it.
The reports are laid out for inline editing, so a sustainability team can correct data in the report instead of raising a ticket for a CSV re-upload.
1. Check your org has Net Zero Cloud.
Setup → Object Manager. You need to see StnryAssetEnvrSrc, StnryAssetCrbnFtprnt,
StnryAssetEnrgyUse, VehicleAssetEmssnSrc, VehicleAssetCrbnFtprnt and
VehicleAssetEnrgyUse. A free Developer Edition org and a standard Trailhead Playground
do not have these — see Orgs that work.
2. Deploy.
sf project deploy start --manifest manifest/package.xml --target-org <alias>Or one click, no CLI:
3. Enable inline editing. Setup → Reports and Dashboards Settings → tick Enable Inline Editing in Reports → Save.
Off by default in most orgs. Without it the reports still run, but read-only.
4. Share the two folders. Reports tab → All Folders → NZC Reports → Share. Same for NZC Dashboards.
Deployed folders are private to whoever deployed them. Give the sustainability team Editor on the report folder.
That's the whole setup. Nothing else to configure, no permission sets, no post-install script.
5 reports you edit directly — tabular, narrow, every column editable in place:
| Report | Fix in place |
|---|---|
| Asset Names and Locations | Site names, city, country, asset type |
| Fleet Names and Types | Vehicle names and types |
| Footprint Data Entry | Reporting year, stage, Scope 1 and Scope 2 figures |
| Energy Use Data Entry | Fuel type, consumption, unit |
| Fleet Energy Data Entry | Fuel type, consumption, distance |
4 reports that find missing records — outer joins, grouped by asset type:
Stationary Assets Missing Footprints · Stationary Assets Missing Energy Use · Fleet Assets Missing Footprints · Fleet Assets Missing Energy Use
4 reports that find orphans — child records whose parent lookup is blank, which a join can never show you:
Orphaned Carbon Footprints · Orphaned Stationary Energy Uses · Orphaned Fleet Footprints · Orphaned Vehicle Energy Uses
An orphaned footprint still contributes to a total. It's a number in your disclosure that nothing explains.
3 summaries — Emissions by Reporting Year, Fuel Consumption by Fuel Type, Fleet Fuel by Fuel Type.
5 audit reports — the part of the CRM Analytics audit dashboard you can rebuild in core Lightning. Emissions by Asset and Year is a matrix, one site per row and one year per column, so a figure that jumped or collapsed between years stands out on a single screen. Footprints by Stage and Footprints by Year and Stage (stationary and fleet) show how much of each disclosure year is still draft or in progress — a number that could still change under audit.
16 report types covering both stationary and fleet, in three shapes each — with
(inner join), with/without (outer join), and standalone. Build your own reports on any of
them; that's rather the point of shipping the source.
3 dashboards — NZC Audit, NZC Data Quality and NZC Emissions Coverage. NZC Audit has a Reporting Year filter across the top, so an admin can audit one disclosure year at a time; the year list is 2023–2026 and is a one-minute edit in the dashboard builder. Every component opens its report, and every report is editable inline where the record exists.
6 list views, optional, for Winter '27 bulk editing — see List views for bulk edits.
Net Zero Cloud ships CRM Analytics dashboards, and those need a separate licence. From the Net Zero Cloud Developer Guide, v67.0 Summer '26, page 1:
The Net Zero Cloud Analytics dashboards are available only for Salesforce Net Zero Cloud users with CRM Analytics for Net Zero Cloud add-on license.
It ships no standard Lightning report types for the emissions objects. You can verify that in your own org:
sf data query --use-tooling-api --target-org <alias> --query \
"SELECT QualifiedApiName, IsReportingEnabled FROM EntityDefinition \
WHERE QualifiedApiName LIKE 'StnryAsset%' OR QualifiedApiName LIKE 'VehicleAsset%'"Every NZC object returns IsReportingEnabled = false, which is the flag governing whether
Salesforce auto-generates standard report types. It's read-only on standard objects, so
there's nothing to switch on. A custom report type isn't a refinement here — it's the only
way to report on Net Zero Cloud data at all.
The limits shaped the report layouts, so they're worth knowing before you promise anything:
| Rule | Consequence |
|---|---|
| Tabular, summary and matrix only | No joined reports. None here are joined. |
| 12 editable fields per row, 100 per report | The data-entry reports are narrow on purpose. |
| Grouping fields are not editable | Group by something you don't need to fix. |
| A lookup that's null across the row can't be edited | You can't create a missing record from a report. |
| FLS and validation rules still apply | A failing edit shows the rule's own message. |
| The field must be on the record's page layout, on the default tab | A column that's greyed out in the report is usually a field that's missing from the layout or sits on a second tab. Winter '27 lifts this for list views only (see below); reports still need the field on the layout. |
That fourth row is why the Missing reports are upload worklists, not fix-it-here reports. If an asset has no footprint record, there's no footprint row to edit. Inline editing fixes what exists; it doesn't conjure records.
Winter '27 adds two User Interface settings (Setup → User Interface), both off by default:
- Make inline edits in list views with multiple record types — a list mixing record types used to turn editing off entirely.
- Remove list view inline edit dependencies on page layout — edit any field you have edit access to, on the layout or not.
With both on, a list view becomes the better bulk-edit surface: edit several rows, save once, no refresh after every cell. The package ships one list view per Net Zero Cloud object with the same narrow columns as the data-entry reports. They're in their own manifest so they never gate the core deploy:
sf project deploy start --manifest manifest/package-4-list-views.xml --target-org <alias> --dry-runAll six validate against a licensed Net Zero Cloud org. They're kept separate anyway, because
they only earn their place once those two settings are on, and because list view column
names are their own name space (see docs/building-your-own.md).
| Org | Free? | Lasts | Notes |
|---|---|---|---|
| NZC trial — Learning org | Yes | 30 days | Pre-configured with sample data. |
| NZC trial — Base org | Yes | 30 days | Licences only. Reports deploy but return nothing until you load data — see sample-data/. |
| Trailhead promo DE org | Yes | Check at signup | Licensed for Agentforce Net Zero. |
| Your own licensed org or sandbox | — | — | Deploy to a sandbox first. |
Salesforce's docs list NZC as available in Enterprise, Performance, Unlimited and Developer Editions. That describes which editions the licence can be added to, not what you get on signup — which is where the afternoon goes.
- A Metadata API deploy of source, not a package install. Nothing appears under Setup → Installed Packages.
- Everything lands as ordinary metadata you own — editable, renameable, deletable. No uninstall button; delete the components.
- All-or-nothing (
rollbackOnError). A failure leaves nothing behind. - Deploying user needs Modify Metadata Through Metadata API Functions or Modify All Data.
No combined emissions total. NZC splits Scope 2 into TotScope2LocBasedEmissions and
TotScope2MktBasedEmissions — two accounting methods for the same emissions, not two
sources. Adding both to Scope 1 double counts. Emissions by Reporting Year reports the
three side by side and leaves the choice of basis to whoever owns the disclosure. Don't
substitute the SuplScope* fields; they measure something different, and using them
produces a report that runs cleanly and reports the wrong number.
Fleet fuel comes from the energy use record. VehicleAssetEmssnSrc has no fuel field —
fuel, consumption and distance all live on VehicleAssetEnrgyUse.
Fifteen of the 21 reports carry no filter, and all 21 leave the standard date filter unbounded. That is a decision, not an oversight, and it is worth understanding before you deploy into an org with years of history.
Why unbounded. The date column available on these objects is CreatedDate — when
somebody typed the record in. The business axis is ReportingYear, and the two do not
agree: a footprint for 2024 is routinely entered in 2026, during the disclosure cycle.
Bounding on CreatedDate would therefore drop records that belong in the answer. It would
make the reports faster and wrong, which is the worse of the two failures for anything
feeding a disclosure.
What it costs. Each of these reports reads every record in scope on every run. On a dev org or a first year of data that is invisible. On an org with several years of footprint and energy-use records it is the first thing that will get slow, and the dashboard-fed reports pay it on every refresh.
What to do about it, when you get there. Add a ReportingYear filter — it is on every
report type here, and it is the axis the reports already group by. Which years to keep is
a question about your disclosure obligations rather than about Salesforce, which is why
this repository does not choose for you.
Two related shapes, also deliberate:
- The six tabular reports have no row limit. They are worklists and lookup lists — Footprint Data Entry, Asset Names and Locations — meant to be worked all the way through. A row limit on a worklist hides the rows somebody still has to fill in.
- The summary reports show details. The same reports are read two ways: as a chart on a dashboard, and as a list of the specific assets to go and fix. Turning details off would make the chart marginally cheaper and the worklist useless.
sample-data/— six UTF-8 CSVs with deliberate gaps and orphans, so the Missing and Orphaned reports return rows on an empty trial org.docs/encoding-evidence/— why accented site names arrive as question marks, and which step is responsible.docs/building-your-own.md— the report type metadata gotchas, for anyone forking this.
.github/workflows/validate.yml checks XML well-formedness, that sf project convert source succeeds, and that every member in every manifest/*.xml has a matching source file.
None of that can see a wrong object or field name. A reference to an object that does not exist produces well-formed XML that converts cleanly and matches the manifest. This repo carried a green badge while referencing five objects that don't exist. Only a deploy against a licensed org proves the names resolve:
sf project deploy start --manifest manifest/package.xml --target-org <alias> --dry-runMIT.