How to fix MISSING_FIELD in Salesforce deployments

A list view, report, or layout references a field that does not exist on the object in the target org.

Surfaces during: metadata deploy validation, for declarative UI components specifically

What it means

MISSING_FIELD shows up when a component, most often a list view, report, or page layout, points to a field API name that Salesforce cannot find on the object in the target org. The field was either never deployed there, was renamed, or was deleted after the dependent component was created.

It's the deploy-time, declarative-metadata counterpart to INVALID_FIELD, which shows up in SOQL and Apex; both trace back to a field reference the target org's schema doesn't currently support, just in different metadata types.

Diagnosis

Common causes

Field renamed or deleted

A custom field was renamed or removed, but list views, reports, or layouts that reference the old API name were never updated.

Field deployed separately

The custom field lives in a different deployment or package and has not reached the target org yet, so dependents deploy before it exists.

Typo in the field API name

The reference uses the wrong object prefix or is missing the __c suffix on a custom field.

The fix

Include the field in the same deploy
Bundle the custom field with the list view, report, or layout that depends on it so both land in the target org together.
Regenerate dependents after a rename
After renaming or recreating a field, re-save or re-export list views and reports that reference it.

Double check the API name

Confirm the field API name is spelled exactly right, including case and the __c suffix, on the correct object.

sf data query --query "SELECT QualifiedApiName FROM FieldDefinition WHERE EntityDefinition.QualifiedApiName = 'Account'" --target-org myOrgAlias

In practice

How Serpent prevents this

Serpent AI scopes tasks by dependency, not just the component you touched, so a list view or report is bundled with the field it needs automatically. See the Salesforce deployment error library.

Metadata and data in one deployment flow in Serpent

Prevention

Deploy list views and reports as part of the same task as the field they reference

Never split a field and its dependent list view, report type, or layout across separate deployment tasks.

Search declarative metadata before renaming any field

Check ListView, Report, and Layout XML for a field's API name before renaming it, not just Apex and Flow.

Retrieve field metadata fresh before editing a list view or report by hand

Pull the current object schema before manually editing XML for a list view or report type, so a stale field name is never carried forward.

Common questions

MISSING_FIELD, answered

Why does this only happen in one sandbox and not another?

The field almost certainly exists in one org and not the other, usually because it was deployed to one environment but not yet promoted to the other.

Does deleting a list view that references a missing field fix the deployment?

It fixes the immediate symptom, but check whether the field or the list view is actually the one that should exist before deleting either; the fix depends on which side of the mismatch is wrong.

Can a report type cause MISSING_FIELD even if the report itself doesn't display the field?

Yes. Report types can reference fields as available columns even when a specific report doesn't use them, and the underlying report type metadata still needs the field to exist.

Start free. No credit card, no install, no commitment.

Set up in under 15 minutes. No DevOps hire needed.

Start free Book a demo