Considerations When Deploying a Single Custom Field
When deploying a custom field, there are two scenarios to keep in mind:
- The Object is New to the Target
- The Object Already Exists in the Target
Scenario 1: The Object is New to the Target
If the custom object is new and only exists in the source org, Gearset will automatically select all custom fields associated with the object for deployment. However, you have the flexibility to choose which custom fields to include.
For example, if you’re deploying a new custom object with several fields, Gearset will select all components by default. If a particular field isn’t ready for deployment, you can open the components menu and deselect that specific field. Since a custom field in Salesforce must belong to a custom object, the object itself will be included in the deployment along with the selected components.
Scenario 2: The Object Exists in the Target
If the custom object exists in both the source and target orgs, you can choose which custom fields you want to deploy.
In this case, a custom object that exists in both the source and target orgs will display metadata for both. You can then select the custom fields you want to deploy.
To deploy a new custom field from the source to the target, you can either select it from the “New items” tab or find it nested under the custom object.
Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more
In Marc Benioff's own words How did salesforce.com grow from a start up in a rented apartment into the world's Read more
Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more
Following swiftly after last week's successful launch of Financial Services Cloud, Salesforce has announced the second installment in its series Read more
