Book Image

Force.com Tips and Tricks

By : Ankit Arora, Abhinav Gupta
Book Image

Force.com Tips and Tricks

By: Ankit Arora, Abhinav Gupta

Overview of this book

<p>Force.com is an extremely powerful, scalable and secure cloud platform, delivering a complete technology stack covering the ground from database and security to workflow and user interface.</p> <p>Force.com Tips and Tricks starts with very basic admin tasks and gradually moves to hard-core coding tips and tricks for the multitenant Force.com platform.</p> <p>The book starts with the basics of Cloud Computing and Principles and constructs of Force.com. The book then swiftly move to detailed coverage of Salesforce analytics.</p> <p>The book also shows how to set up development environments and and gives detailed understanding of tools and destinations that every Force.com developer should know. The book also covers important administration concepts where you gain vital information for key topics such as schema and reporting for an organization. For Force.com, troubleshooting a problem and code reuse are two important aspects that help in boosting productivity, a complete chapter is dedicated to these tasks.</p> <p>This book takes you beyond any documentation or course and promises hands-on expertise.</p>
Table of Contents (15 chapters)
Force.com Tips and Tricks
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Migrating changes between environments


Migration refers to the movement of configuration changes from one Salesforce org to another. This is done either to keep orgs in sync or to move changes through dev orgs to production or the packaging org. Packaging org is the DE org that you use to create your final packages. For the sake of simplicity, we will refer to both the packaging org and production org as the production org.

Migration can happen either manually or via metadata.

Broadly, the steps to migrate changes are as follows:

  1. Determine components—some may be migrated through metadata while others will be required to be moved manually.

  2. Migrate components in the desired order maintaining dependency.

  3. Optionally modify your Force.com project or outbound change set to deploy only a subset of components.

  4. Deploy.

Migrating changes manually

Those components that are not available via API need to be migrated manually and this is achieved by performing setup changes through the Salesforce user interface...