Clayton

Record IDs change between environments. For this reason, any logic that uses hardcoded IDs will fail when deployed to a different Salesforce environment.

<a href="https://help.salesforce.com/s/articleView?id=sf.flow_prep_bestpractices.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Flow Best Practices</a>

<a href="https://admin.salesforce.com/blog/2021/why-you-should-avoid-hard-coding-and-three-alternative-solutions" rel="nofollow noopener noreferrer" target="_blank">Why You Should Avoid Hard Coding and Three Alternative Solutions</a>

- <a href="https://help.salesforce.com/s/articleView?id=sf.flow_prep_bestpractices.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Flow Best Practices</a>
- <a href="https://admin.salesforce.com/blog/2021/why-you-should-avoid-hard-coding-and-three-alternative-solutions" rel="nofollow noopener noreferrer" target="_blank">Why You Should Avoid Hard Coding and Three Alternative Solutions</a>

Detect the use of hardcoded record IDs within Flows.

Hardcoded ID (flows)

Home

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

Track the progress of all tickets related to your company

Tickets portal

{assigneeName} needs more information from you

Resources