Book Image

Salesforce CRM - The Definitive Admin Handbook - Fourth Edition

Book Image

Salesforce CRM - The Definitive Admin Handbook - Fourth Edition

Overview of this book

Salesforce CRM’s Winter ’17 release offers a host of new features for CRM designed to transform your sales and marketing requirements. With this comprehensive guide to implementing Salesforce CRM, administrators of all levels can easily acquire deep knowledge of the platform. The book begins by guiding you through setting up users and the security settings and then progresses to configuration, data management, and data analytics. We swiftly move on to the setting up of organization wide features that affect the look and feel of the application. Process automation and approval mechanisms are covered next, along with the functional areas of Sales Cloud, Service Cloud, Marketing Cloud, and Salesforce Chatter. This book details Salesforce CRM system administration in a practical way and is an invaluable reference for both new administrators and experienced professionals. At the end of the book, techniques to further enhance the system and improve the return on investment Salesforce mobile apps and mobile administration are covered, along with Salesforce Adoption Manager. Every chapter is complete with a section containing example questions of the type that you might encounter in the certification examination.
Table of Contents (18 chapters)
Salesforce CRM - The Definitive Admin Handbook - Fourth Edition
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface

Custom field governance


Controlling the creation of fields is necessary to avoid adding unnecessary new fields in Salesforce. Without appropriate field creation governance, there is a risk of producing an application with a complex data structure that provides a poor user experience.

This issue can often be observed due to the ease of creating new custom fields. However, there are other causes such as:

  • Configuring spontaneous responses to end-user field creation requests without gathering full requirements

  • Lack of specification or understanding of reporting requirements for field usage

  • Creation of fields that are too specific for common uses, thus driving the need to create ever more fields

  • Lack of knowledge or awareness of existing fields that could be used rather than creating new ones

As the number of unnecessary fields increases, users will find it ever more difficult to enter the correct data into the correct fields. Therefore, the amount of entered data is reduced along with user's satisfaction...