---
schema_version: "1"
id: ad9861d12abe2c303dfe7db72672cf41aa67ef6ff3a537ee017588cc69dcbbd0
title: Validate a Change Set
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/changesets_inbound_test_deploy.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.changesets_inbound_test_deploy.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7875ba05181cf1a721f6cb7a51e6ad4eed65786eb03536470f709b7ab0d7b57e
description: You can validate a change set without deploying changes. By validating you can view the success or failure messages you receive with an actual deploy.
products:
  - Salesforce Platform
release: "264"
---
# Validate a Change Set

You can validate a change set without deploying changes. By validating you can view the success or failure messages you receive with an actual deploy.

We recommend starting a validation during off-peak usage time and limiting changes to your org while the validation is in progress. The validation process locks the resources that are being deployed. Changes you make to locked resources or items related to those resources while the validation is in progress can result in errors.

1. From Setup, enter Inbound Change Sets in the Quick Find box, then select **Inbound Change Sets**.
2. Click **Validate** next to the change set you want to validate.
    
    To review the change set before validating it, click the name of the change set to view its detail page. When ready, click **Validate**. If the change set has been deleted from its source org, the **Validate** link isn’t available. If a deployment of the change set is in progress, the **Validate** link isn’t available until after the deployment completes.
3. After the validation completes, click **View Results**.

If you change a field type from Master-Detail to Lookup or vice versa, the change isn’t supported when using the **Validate** option to test a deployment. This change isn’t supported for test deployments to avoid data loss or corruption. If a change that isn’t supported for test deployments is included in the deployment package, the test deployment fails and issues an error.

If your deployment package changes a field type from Master-Detail to Lookup or vice versa, you can still validate the changes before you deploy to production. Perform a full deployment to another test sandbox. A full deployment includes a validation of the changes as part of the deployment process.

Change sets that have been successfully validated can qualify for a quick deployment. For more information, see [Quick Deployments](https://help.salesforce.com/s/articleView?id=platform.deploy_monitoring.htm&release=264.0.0&type=5).

#### See Also

- [View Inbound Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_inbound_view_list.htm&release=264.0.0&type=5 "The Inbound Change Sets page lists change sets awaiting deployment, as well as the history of deployed change sets.")
- [Viewing Change Set Details](https://help.salesforce.com/s/articleView?id=platform.changesets_inbound_view_detail.htm&release=264.0.0&type=5 "The Change Sets detail page lists information about a particular change set.")
- [Deploy a Change Set](https://help.salesforce.com/s/articleView?id=platform.changesets_inbound_deploy.htm&release=264.0.0&type=5 "You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.")