Field Usage
SchemaForce surfaces usage and dependency signals for every field — so the fields nobody remembers building become a clear, safe cleanup list instead of guesswork.
See field population signals, where a field is referenced, and governance-lite checks like PII-looking and likely-duplicate fields — the inputs you need before deciding what to retire.
Pair usage with dependencies so you remove the right things — and, with change tracking, keep a record of what changed. Deeper impact analysis (“what breaks if I change this field?”) is on the way.
SchemaForce surfaces dependency references today; a dedicated impact-analysis view (“what breaks if I change this?”) is in progress. Use dependencies plus change tracking in the meantime.
Connect Salesforce, explore every object and field, and ask your schema anything — free to start.