Rule registry · FL-003

No hardcoded IDs

Checked by the Salesforce Flow scan. Severity high.

FL-003HighReliability

What it requires. Flows must not contain hardcoded Salesforce record IDs for Record Types, Queues, Owners, Groups, or any other org-specific records.

Why it matters. Record IDs differ between environments (Dev, QA, UAT, Production). Hardcoded IDs cause flows to fail silently or throw errors when deployed across environments. They are invisible to reviewers scanning for environment-specific dependencies.

How to fix it. Replace hardcoded IDs with a Get Records lookup using the DeveloperName field on the relevant setup object (RecordType, Group, etc.), or store the developer name in Custom Metadata and retrieve it at runtime.

Source. Salesforce Admins: The Ultimate Guide to Flow Best Practices and Standards – Hard coding IDs: use Get Records on DeveloperName or Custom Metadata instead

Is this rule worth checking?

Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.

Every rule we check, every source, and every one we turned down