We’ll be using a standard Salesforce feature called change sets to deploy. Step 0: Connect your Sandbox and Production orgs Setup >> Deploy >> Deployment Connections You’ll only need to do this once!
Step 1: Navigate to the Outbound Change Sets page in Sandbox Setup >> Deploy >> Outbound Change Sets
Step 2: Add all necessary components to a new change set, then upload to Production In this case, we’ll add both the ForceForecasting trigger and the TestForceForecasting Apex class. We can add tons of other things like custom objects and fields, but don’t worry about that for now!
Step 3: Login to your production org, find the Inbound Change Set, and deploy! Setup >> Deploy >> Inbound Change Sets
Once you hit the “Deploy” button (no need to validate!), you’ll have to wait a few minutes for the changes to go through. Grab yourself a nice cup of coffee while you wait and give yourself a pat on the back for deploying your first trigger!
We’ll be using a standard Salesforce feature called change sets to deploy. Step 0: Connect your Sandbox and Production orgs Setup >> Deploy >> Deployment Connections You’ll only need to do this once!
Step 1: Navigate to the Outbound Change Sets page in Sandbox Setup >> Deploy >> Outbound Change Sets
Step 2: Add all necessary components to a new change set, then upload to Production In this case, we’ll add both the ForceForecasting trigger and the TestForceForecasting Apex class. We can add tons of other things like custom objects and fields, but don’t worry about that for now!
Step 3: Login to your production org, find the Inbound Change Set, and deploy! Setup >> Deploy >> Inbound Change Sets
Once you hit the “Deploy” button (no need to validate!), you’ll have to wait a few minutes for the changes to go through. Grab yourself a nice cup of coffee while you wait and give yourself a pat on the back for deploying your first trigger!
Please refer to the below links for the information
Deploying to production:https://developer.salesforce.com/docs/atlas.en-us.dev_lifecycle.meta/dev_lifecycle/deploy.htm Deploying components to production:https://developer.salesforce.com/ docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_deploy.htm Deployment checklist and Best Practices:http://www.docurated.com/all-things-productivity/salesforce-deployment-checklist Steps for easy deployment:https://www.sundoginteractive.com/blog/five-steps-to-easier-deployments-with-salesforce
1. Zip the files you would like to deploy in file explorer/whatever your os refers to it as: Select the desired files you would like to deploy all at once > right click > compress them into a single zip file
Team i am working on SalesforceDX for deployments.Starting working on scratch orgs and can pull the changes to local disk to sync changes I used the commands in the processing of Add and commit and push. It is saying that everything is upto date and i couldn't see my changes in my local git develop branch or couldn't see any change in my branch as well.
1) https://developer.salesforce.com/docs/atlas.en-us.dev_lifecycle.meta/dev_lifecycle/deploy.htm
2) https://developer.salesforce.com/trailhead/en/alm_deployment/alm_tools
3) https://www.sundoginteractive.com/blog/five-steps-to-easier-deployments-with-salesforce
4) http://www.sfdc99.com/2013/06/04/how-to-deploy-code-from-sandbox-to-production/
We’ll be using a standard Salesforce feature called change sets to deploy.
Step 0: Connect your Sandbox and Production orgs
Setup >> Deploy >> Deployment Connections
You’ll only need to do this once!
Step 1: Navigate to the Outbound Change Sets page in Sandbox
Setup >> Deploy >> Outbound Change Sets
Step 2: Add all necessary components to a new change set, then upload to Production
In this case, we’ll add both the ForceForecasting trigger and the TestForceForecasting Apex class. We can add tons of other things like custom objects and fields, but don’t worry about that for now!
Step 3: Login to your production org, find the Inbound Change Set, and deploy!
Setup >> Deploy >> Inbound Change Sets
Once you hit the “Deploy” button (no need to validate!), you’ll have to wait a few minutes for the changes to go through. Grab yourself a nice cup of coffee while you wait and give yourself a pat on the back for deploying your first trigger!
Tool for deployment:-
Let us know if this will help you
All Answers
1) https://developer.salesforce.com/docs/atlas.en-us.dev_lifecycle.meta/dev_lifecycle/deploy.htm
2) https://developer.salesforce.com/trailhead/en/alm_deployment/alm_tools
3) https://www.sundoginteractive.com/blog/five-steps-to-easier-deployments-with-salesforce
4) http://www.sfdc99.com/2013/06/04/how-to-deploy-code-from-sandbox-to-production/
We’ll be using a standard Salesforce feature called change sets to deploy.
Step 0: Connect your Sandbox and Production orgs
Setup >> Deploy >> Deployment Connections
You’ll only need to do this once!
Step 1: Navigate to the Outbound Change Sets page in Sandbox
Setup >> Deploy >> Outbound Change Sets
Step 2: Add all necessary components to a new change set, then upload to Production
In this case, we’ll add both the ForceForecasting trigger and the TestForceForecasting Apex class. We can add tons of other things like custom objects and fields, but don’t worry about that for now!
Step 3: Login to your production org, find the Inbound Change Set, and deploy!
Setup >> Deploy >> Inbound Change Sets
Once you hit the “Deploy” button (no need to validate!), you’ll have to wait a few minutes for the changes to go through. Grab yourself a nice cup of coffee while you wait and give yourself a pat on the back for deploying your first trigger!
Tool for deployment:-
Let us know if this will help you
Please refer to the below links for the information
Deploying to production:https://developer.salesforce.com/docs/atlas.en-us.dev_lifecycle.meta/dev_lifecycle/deploy.htm
Deploying components to production:https://developer.salesforce.com/
docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_deploy.htm
Deployment checklist and Best Practices:http://www.docurated.com/all-things-productivity/salesforce-deployment-checklist
Steps for easy deployment:https://www.sundoginteractive.com/blog/five-steps-to-easier-deployments-with-salesforce
Please mark it as solved if it helps you.
Best Regards,
Nagendra.P
Select the desired files you would like to deploy all at once > right click > compress them into a single zip file
2. navigate to: https://workbench.developerforce.com/login.php
- As the environment select production & keep the API version as the current one already displayed on the page
- Agree to the terms of service > click login with salesforce >Hover over the migration tab > click deploy
- Click choose file > choose the zip file you recently created.
Choose what you would like from the picklist values, I typically select: ignore warnings, rollback on error, and single package- test Level is No TestRun
click next> next > deploy3. Voila ! If your deployment was successful the submitted materials (classes, objects, and etc.) should be present in the production org.
Let me know if this worked for you and if so feel free to give it a thumbs up/mark as solved,
Esther Onema
source: https://www.youtube.com/watch?v=CyWSAeQbANQ