# CRM permissions make an invisible field look empty

When a sync loses read access to a field, that field reads as null.

By Ki Moon · 2026-10-21 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/invisible-field-looks-empty/

**Symptom:** A CRM field goes blank on every new record after one date, older values stop moving, and the sync logs no error.

A connector reads a CRM through one integration user and sees only the fields that user can see, so a single permission-set change can hide dozens of fields at once.

To the sync, a field it can no longer see looks exactly like a field that is empty. A connector that builds its query from the schema simply stops asking for the field, so no error is logged and the values stop arriving.

Incremental sync makes it worse. It re-reads only rows edited since the last run, so values captured before the change freeze in place and never refresh. Fivetran's Salesforce connector FAQ says that after a column's permission is removed and then granted again, only new records sync and older values need a table re-sync.

A history of each object's schema, snapshotted on every sync, tells the two apart. In such a history, a permission change shows as a single transition where many fields vanish at once, while the record values show nothing.

## Check your setup (read-only)

Read the CRM's field permission metadata today. List the fields your integration user can read on each synced object. Compare that list with the field list your first full sync captured. Any field in the old list that is missing now is a gap.

**Passes if:** Every field your first full sync captured is still readable by the integration user today, on every synced object.

**Access needed:** crm-read, local-config

## If it fails (changes to make later, not part of the check)

1. Snapshot each synced object's field list on every sync run and keep the history.
2. Treat a previously synced field that disappears from an object's schema as an incident, never as a column of nulls.
3. Alert the CRM admin and the data owner within the hour a synced field vanishes.
4. Run a full re-sync of the object after access is restored. Incremental sync never revisits records edited before the gap.
5. Check that the field is still in the integration user's schema before reading a null as empty.

**Applies if:** A job reads or fills CRM contact fields through an integration user whose permissions an admin outside your team controls.

**Skip if:** Your sync config reads only standard fields, through a system-administrator user that no one else manages.

Tags: crm, data quality, freshness
