# Direct production changes and field type risks

*Platform Development Lifecycle and Deployment Architect Study Guide · Operating · Last updated October 26, 2026 · https://www.certifyforce.com/study-guide/platform-development-lifecycle-and-deployment-architect/operating/direct-production-changes-and-field-type-risks*

Which requests are safe to make directly in production and which must go through a sandbox pipeline, why field type changes lose data or are blocked, how configuration edits take effect at once and get overwritten by the next deployment, and why timing and freezes matter.

- Certification: Salesforce Platform Development Lifecycle and Deployment Architect
- Exam section: Operating
- Study guide: https://www.certifyforce.com/study-guide/platform-development-lifecycle-and-deployment-architect

**Official exam objective:**

> Given a detailed customer environment scenario including a specific request, explain the implications for incorporating the request directly in a production environment.

## What the exam expects

- Decide whether a request can be made directly in production or must be built in a sandbox and promoted, and explain what skipping the pipeline gives up.
- Predict what a field type change does to data, external IDs, encrypted fields and the Apex or flows that reference the field.
- Explain why configuration edited in production (validation rules, custom metadata records) affects users and integrations at once, and what the next deployment does to it.
- Recommend when a change should run, given peak usage, record locking and change freezes.

Key terms: **direct production change** (a change made in production's Setup or data instead of deployed through the pipeline), **field type conversion** (changing a custom field's data type in place), **external ID** (a field an upsert matches records on), **release moratorium** (a planned period with no releases), **row lock** (a record lock that makes a competing save fail).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Apex in production | Can't be developed there; use a sandbox, scratch org or Developer Edition org | [Deploying Apex](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying.htm) |
| Fine directly in production | Email templates, users, permission sets and profiles | [Deployment Best Practices](https://help.salesforce.com/s/articleView?language=en_US&id=platform.deploy_best_practices.htm&type=5) |
| Suggested governance | Limit Customize Application to admins; few users with deploy permissions | [Deployment Best Practices](https://help.salesforce.com/s/articleView?language=en_US&id=platform.deploy_best_practices.htm&type=5) |
| Change set reach | Any orgs affiliated with the same production org; no records | [Change Sets](https://help.salesforce.com/s/articleView?language=en_US&id=sf.changesets.htm&type=5) |
| Blocked type changes | Referenced by Apex, Visualforce, processes or flows; lead conversion mapping; Shield-encrypted | [Considerations for Converting the Field Type](https://help.salesforce.com/s/articleView?id=platform.notes_on_changing_custom_field_types.htm&type=5) |
| External ID survives conversion | Only to text, number or email | [Considerations for Converting the Field Type](https://help.salesforce.com/s/articleView?id=platform.notes_on_changing_custom_field_types.htm&type=5) |
| Conversion limit and duration | 85 million field type conversions for a deploy() or package upgrade; some conversions run over 24 hours | [Considerations for Converting the Field Type](https://help.salesforce.com/s/articleView?id=platform.notes_on_changing_custom_field_types.htm&type=5) |
| Validation rules | Run whatever the data source, including API and Data Loader | [Operational Excellence](https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence.html) |
| Next deployment | Creates or updates the components it contains | [deploy()](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm) |

## Check yourself

- Why does a field type change in production threaten more than the field's own data?
- When is a change fine to make directly in production rather than through the sandbox pipeline?
- What happens to list views built on a field whose conversion loses data?
- Why can a bulk record update fail when run during peak hours?

## Sources

- [Deployment Best Practices](https://help.salesforce.com/s/articleView?language=en_US&id=platform.deploy_best_practices.htm&type=5)
- [Considerations for Converting the Field Type of a Custom Field](https://help.salesforce.com/s/articleView?id=platform.notes_on_changing_custom_field_types.htm&type=5)
- [Deploying Apex](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying.htm)
- [Operational Excellence (Well-Architected)](https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence.html)
- [Reliability (Well-Architected)](https://architect.salesforce.com/docs/architect/well-architected/guide/reliability.html)
- [Change Sets](https://help.salesforce.com/s/articleView?language=en_US&id=sf.changesets.htm&type=5)
- [deploy() (Metadata API)](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm)
- [Monitor Setup Changes with Setup Audit Trail](https://help.salesforce.com/s/articleView?language=en_US&id=sf.admin_monitorsetup.htm&type=5)
- [project retrieve start (CLI command reference)](https://developer.salesforce.com/docs/platform/salesforce-cli-reference/guide/cli_reference_project_retrieve_start.html)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 11 linked practice questions, and unlimited timed mock exams are included with the Platform Development Lifecycle and Deployment Architect pack (USD $19): https://www.certifyforce.com/practice-exams