There’s a common mantra in the Salesforce world: Never configure anything directly in Production.
Generally, this is a good idea, but we’ve all broken this standard. And probably more than once 😉
So, when is it OK to configure something directly in Production?
- When the problem is only in Production. It’s hard to solve a problem that doesn’t appear in any sandbox. So if the issue is only with Production, then your options are limited.
- When it’s a minor change. The definition of minor is a bit relative, so use common sense here. If it’s to correct a spelling mistake or to change the location of a field on a page, that’s OK. Be very cautious with anything more complex.
- When you’re installing a package and you know it well. It’s OK to install a package before creating or refreshing sandboxes, since those sandboxes will receive the package. You’re saving installation steps. It’s also OK when you know the package won’t impact current operations and requires a few steps to set up and use. This is a gray area though, so proceed with caution.
The takeaway
You know configuring directly in Production is a taboo. But like all taboos, sometimes they are fun to break. Just think about what you’re doing for a moment before carefully proceeding.
Under what conditions do you configure directly in Production?
Category:
Salesforce