Find the Salesforce fields, flows and validation rules only your senior can explain
Today I wrote on LinkedIn about something you never forget in your career: the person who knew far more than you and, instead of making you feel it, sat down to teach you. Good seniors do that. But in a Salesforce org, a lot of what they teach is never written anywhere. Why does this field exist? Who asked for this flow? What is this validation rule protecting? The answer lives in one or two…
This LinkedIn post explains how to identify Salesforce custom fields, active flows, and active validation rules that lack descriptions. Such items are crucial to understand because their purpose often resides in the memory of senior administrators, and their absence can lead to confusion for new users. The author provides three Tooling API and SOQL queries, along with a few lines of Python code using the pandas library, to generate a list of these components.
The output includes the component type (field, flow, or validation rule), the component name, the administrator who last modified it, whether it is still active, and the last change date. By presenting this list, the author aims to facilitate a discussion between senior administrators and new users, enabling the latter to better understand the Salesforce environment they are working with.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
