Book Image

Mastering Apex Programming

By : Paul Battisson
5 (1)
Book Image

Mastering Apex Programming

5 (1)
By: Paul Battisson

Overview of this book

As applications built on the Salesforce platform are now a key part of many organizations, developers are shifting focus to Apex, Salesforce’s proprietary programming language. As a Salesforce developer, it is important to understand the range of tools at your disposal, how and when to use them, and best practices for working with Apex. Mastering Apex Programming will help you explore the advanced features of Apex programming and guide you in delivering robust solutions that scale. This book starts by taking you through common Apex mistakes, debugging, exception handling, and testing. You'll then discover different asynchronous Apex programming options and develop custom Apex REST web services. The book shows you how to define and utilize Batch Apex, Queueable Apex, and Scheduled Apex using common scenarios before teaching you how to define, publish, and consume platform events and RESTful endpoints with Apex. Finally, you'll learn how to profile and improve the performance of your Apex application, including architecture trade-offs. With code examples used to facilitate discussion throughout, by the end of the book, you'll have developed the skills needed to build robust and scalable applications in Apex.
Table of Contents (21 chapters)
1
Section 1 – Triggers, Testing, and Security
8
Section 2 – Asynchronous Apex and Apex REST
15
Section 3 – Apex Performance

Dynamic parsing using custom metadata

In the examples so far, we have let Apex do most of the heavy lifting for us in translating our request body into Apex data types for us to work with. In this section, we will look at how we could do this manually.

We want to be able, at runtime, to determine how we should map the data provided to us to different fields within Salesforce. To do this, we will be using a custom metadata type.

In the following screenshot, you can see the definition for my API Mapping custom metadata type. I have added an additional Target Field text field on to the metadata type, so we can create records using the DeveloperName field to hold the API property, and the Target_Field__c field to hold the API name of the field to populate:

Figure 12.2 – API Mapping custom metadata type definition

Next, I have created two records to allow us to map the fields we were previously working with in our examples. You can see these in the...