Wrapper Class in Salesforce Tutorial

What is Wrapper Class in Salesforce?

You learned about Salesforce in-depth in the previous sections of this Salesforce tutorial. Let’s now learn ‘What is a wrapper class in Salesforce?’

A wrapper class is nothing but a collection of different Salesforce data types. In Salesforce, you can combine multiple data types and utilize them for various purposes. For example, there is a wrapper class that can access the account records and display an in-page block table. You have an option of a checkbox, and you can associate multiple serial numbers to display the number of records. So, there can be multiple records and respective serial numbers.

When elucidating the architecture of Salesforce, you can see that it is somewhat similar to a database wherein the records are defined as rows, the fields are determined as columns, and the objects are defined as tables. Having different collections of classes assigned to facilitate a successful development process, Salesforce possesses the MVC architecture.

MVC Architecture

Salesforce UI has a Model-View-Controller (MVC) model, and here metadata is stored to view it as XML later. A build-up of Visualforce pages and lightning components that can be used as needed comprises the view layer. A controller is basically an Apex Class extended to the controller; data is relinquished to accessible models first to view the elements. Developers are limited to a data structure of a particular object type while the relationship between these data structures is necessary. In order to handle various objects collectively, you will need only a single object for an individual field. This condition might be confusing in the beginning, but some practice will help you get through this.

Following image shows the MVC architecture in Salesforce:

There are two types of controllers: standard controllers and custom controllers. Controllers are responsible for modeling and viewing objects, components, and pages.

As can be seen from the image above, a single contact can have many orders wherein each order can have various order lines. This kind of nested structure is exemplified through a JSON or NoSQL database.

Wrapper Class in Salesforce as a Solution

What is a wrapper class in Salesforce? A wrapper class is used mainly to wrap data collected from the present objects to a new object. An sObject is defined as a distinct type that doesn’t include a database or any relevant field; it doesn’t have any API page but is definitely a valid object.

In other orders, a wrapper class is a container class; it is a data structure and an abstract data type that contains various objects and their members together. A wrapper class is also called a custom object which is determined by a developer with a particular set of properties, e.g., a custom class in Salesforce contains fields and each field has a definite data type. Similarly, a wrapper class is also a custom class that has various properties and data types, which can be determined according to the requirement. If you want to wrap various data objects, there is no better option than wrapper classes in Salesforce.

Advantages of a Wrapper Class in Salesforce

• When considering the JSON structure, the wrapper class structure is comparable to the data visualization technique on a particular web page.
• There isn’t any requirement for passing the map structure for browsing elements or for managing the relationship between objects.
• If you want to pass an sObject, there isn’t any penalty for the same, and it can also be extendable to the class constructors.
• Data can be organized perfectly when it is nested.

A wrapper class and a container class can be kept together, but it is better if they are stored separately. When they are kept independently, it is easy for them to be maintained and reused whenever required, thus preventing code duplication.

Therefore, it is clear enough that a wrapper class is used to construct a new object within the Apex code which can consolidate a set of fields that are most importantly required at the runtime or various fields from different objects. This provides extra control and flexibility over the data objects to view and control the elements.

Wrapper Class as an Everyday Tool in Salesforce

Let’s now talk about why wrapper class is described as an everyday Salesforce tool. By saying that it means, all Salesforce Developers use wrapper classes, along with other Salesforce tools, on a daily basis. This is normal in Visualforce wherein some of the queries are performed on the data before presenting it to the user.

A few activities included are as follows:

• Connecting values concurrently for various fields of an object using a mapping table
• Presenting various threads of data mutually in a single list
• Enhancing a data object by extracting the data from another object

The most suitable solution for all these concerns is wrapper classes. Every wrapper class can have different specifications as designed, which is based on its user terms, but the comprehensive structure is more manageable for all of the wrapper classes.

A wrapper class doesn’t have an inner class determined by default, yet the practice of having an inner class can be more efficient and simple in Salesforce. A wrapper class is used similarly as unions, structures, or algebraic types for any other class; the method is limited with a bounded introspection and with possible dynamism in Apex.

In order to construct any powerful wrapper class, you should use properly designed properties in your wrapper class rather than opting for a highly complex rendering. Also, have in mind that there is a huge requirement for enforcing support manually so that the data restructuring can come with some particular obligation to enforce all the permissions properly.

Sorting Wrapper Class Collection in Apex

A predefined functionality in Apex is used to classify fundamental data types in Salesforce. A lot of developers have faced this situation wherein they had to classify the custom data types according to force.com. Still, how would force.com know about the sorting of a class? And, how would it know the data usage within a class?

The Verdict

A wrapper class is a proven enhancement of growth for Salesforce Developers with its wider range of solutions, along with its functionalities. It is used everywhere, and Salesforce Developers have realized its benefits too.

Whenever you want to compare custom objects or you need to add more functionalities, you can try using wrapper classes in your own way. You can also add many fields within an object whenever required and maximize the usability of an application. With this, we come to the end of this section on ‘What is wrapper class in Salesforce?’

Learn On-Demand Salesforce Training with Advanced Concepts By Industry Experts

• Instructor-led Sessions
• Real-life Case Studies
• Assignments

Explore Curriculum

Salesforce Governor Limits

Governor limits in Salesforce are used to ensure the effective use of resources on the Force.com multi-tenant platform. In order to execute the code efficiently, Salesforce.com sets some limits.

Before continuing, let’s take a look at what you will learn in this tutorial on Governor Limits in Salesforce:

1.Salesforce Governor Limits

2.What are Governor Limits

3.Types of Governor Limits

• Per-transaction Certified Managed Package Limits
• Static Apex Limits
• Per-transaction Apex Limits
• Lightning Platform Apex Limits
• Size-specific Apex Limits

4.Advantages of Governor Limits in Salesforce

5.How can we avoid Salesforce Governor Limits?

What are Governor Limits?

To ensure that no one acquires resources from others, Force.com sets many restrictions that limit normal code execution. Salesforce has to do this because of its multi-tenant architecture, where all organizations and customers share a single resource. If one of the governor limits is not met, an error will be raised and the program will stop or halt. Therefore, it is important to ensure that our code is scalable and does not violate governor limits. These limits are called the single transaction basis, a single trigger execution.

Types of Governor Limits in Salesforce

• Per-transaction Certified Managed Package Limits
• Static Apex Limits
• Per-transaction Apex Limits
• Lightning Platform Apex Limits
• Size-specific Apex Limits

Per-transaction Certified Managed Package Limits

Certified managed packages are managed packages that have passed AppExchange security checks for most transaction limits. Certified managed packages are developed by Salesforce ISV partners and installed in our org from AppExchange under a unique namespace.

With this governor limit, there is no limit to the number of certified namespaces that can be accessed through a single transaction. However, the prerequisite is that the number of operations that can be performed in a single namespace does not exceed the per-transaction limits. In addition, the total number of operations that can be performed in any transaction across the namespace is limited. The total limit for each namespace is 11 times. Shared limits on all namespaces are not affected by collective limits, such as a limit on maximum CPU time.

All transaction limits count individually for certified managed packages expect:

• Maximum CPU time
• Total heap size
• Maximum number of unique namespaces
• Maximum transaction execution time

Each of these limits applies to all transactions, even as the number of certified managed packages running in the same transaction. If we install an AppExchange package created by an uncertified Salesforce ISV partner, the code for that particular package will not have its own governor limits. All resources used by the package are counted toward the total governor limit of the org. All collection resource messages and warning messages are also generated based on the corresponding package namespace.

Static Apex Limits

So far, we know that there are different governor limits for each description we give in Apex. There are more governor limits for Static Apex, i.e., for different kinds of callouts, queries, loops, records, and batch sizes, along with different transactions. Let’s look at these limits individually:

Enroll in Salesforce Certification Course to UPGRADE Your Skills

Weekday / Weekend BatchesSee Batch Details

Per-transaction Apex Limits

Per-transaction Apex Limits are used for counting each Apex transaction. When we talk about Batch Apex, these specific limits in the execution method for executing each batch of records will be reset. The following table summarizes the limits for the synchronous and asynchronous Apex:

Lightning Platform Apex Limits

The following limits do not apply to Apex transactions and are therefore managed by the Lightning platform.

Size-specific Apex Limits

Size-dependent Apex Limits are specifically designed to ensure that there are no oversized items in classes, triggers, org, etc.

The following table gives the limits for each of these:

Advantages of Governor Limits in Salesforce

• Governor limits in Salesforce prevent other orgs from using and hence executing lengthy code, which can take up a lot of space in the memory and even the entire cloud CPU.
• Apex has completely different or unique coding limits.
• These governor limits help us stay in the right space of coding with Apex.

How can you avoid Salesforce Governor Limits?

As a developer, we need to ensure that our code is scalable and does not exceed the governor limits. But how? Follow this process to meet the governor limits in Salesforce:

• Do not have DML statements or SOQL queries in our FOR loop
• Try not to use SOQL or DML operations in the loop
• Try to bulkify the code and helper methods
• Query large data sets
• Use Batch Apex if we want to process 50,000 records
• Streamline various triggers on the same object
• Use streamlining queries and collections for loops