FindingcurrentGTM data

CRM permissions make an invisible field look empty

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

SymptomA 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 ifEvery field your first full sync captured is still readable by the integration user today, on every synced object.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Snapshot each synced object's field list on every sync run and keep the history.
  2. 02Treat a previously synced field that disappears from an object's schema as an incident, never as a column of nulls.
  3. 03Alert the CRM admin and the data owner within the hour a synced field vanishes.
  4. 04Run a full re-sync of the object after access is restored. Incremental sync never revisits records edited before the gap.
  5. 05Check that the field is still in the integration user's schema before reading a null as empty.
Applies ifA job reads or fills CRM contact fields through an integration user whose permissions an admin outside your team controls.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.