Blog

Most field descriptions in an old Salesforce org are blank. How to inventory them with the Tooling API, bulk-deploy through the Metadata API — and the real bottleneck no tool solves: actually writing them.

When a user can't see a Salesforce field, field-level security is only one of five layers. How to tell whether it's FLS, page layout, record type, or record sharing — fast.

Salesforce blocks a field delete one dependency at a time. How to find every reference up front — the Where is this used? button, the Dependency API, and a metadata grep — and what each one misses.

Salesforce points you toward permission sets, but moving off profiles means proving the new setup grants exactly what the old one did. How to compare a profile and a permission set, field by field.

Salesforce makes field usage hard to see. How to find the fields nobody fills in, why empty isn't the same as safe to delete, and how to retire them with the dependencies in front of you.

Auditing who can see a Salesforce field means checking every profile and permission set — or one SOQL query against FieldPermissions. The manual method, the faster query, and the one-screen answer.

"Is this field safe to change?" is one of the hardest questions in Salesforce. Field-level impact analysis traces the automations, reports, and dependencies that rely on a field — so you can change it with confidence.

Schema drift is the slow accumulation of changes nobody tracked — until a report breaks or an integration fails. Here's why the audit trail isn't enough and what real change tracking looks like.

Manual documentation decays the moment you save it. Here's why org documentation goes stale, why spreadsheets can't keep up, and what living documentation looks like instead.