Kaizen #54 - Subforms vs. Related Lists

Hello everyone!

Welcome back to another week of Kaizen.

In this post, we will analyze how to choose between a subform and a related list based on your business case.

What will you learn from this post?

When to choose a subform?
When to choose a related list?
Comparing subforms and related lists

1. When to choose a subform?

Subforms are used to organize details in a record based on your business needs. Every line item is a subform record. To know more about subforms, refer to Kaizen #31 - Subforms #API.

1a. Business case

For instance, consider a scenario where you want to view all the necessary details of the stakeholders of an account, such as email ID, phone number, and so on while viewing an account record.

For this, go to Setup > Modules and Fields > Accounts > Choose the desired layout and add a subform named "Stakeholders". In this subform, you can have a lookup field that points to Contacts (Stakeholders). You can further choose to add new fields or add fields from the Contacts module to the subform.

Adding fields from the Contact module to the subform:

Adding new/additional fields to the subform (it can be any of any field-type including aggregate/formula):

The system auto-populates the details of the stakeholder, based on the stakeholder name. Thus, allowing you to view all the necessary details of a stakeholder in a single glance. If needed, you can even add aggregate/formula fields to the subform.

Note:

The system automatically populates the values only if the value is present in that field in the child record.

For other sample business use cases, click here.

1b. Retrieving subform records along with parent record.

You can retrieve subform records only when you retrieve records with their unique ID. The system does not retrieve subform records when you retrieve all the records in a module, or perform a search operation.

Request URL: {{api-domain}}/crm/v2/Accounts/4150868000003247001

Request Method: GET

Sample Response:

You can also choose to retrieve just the subform records using Get Subforms API.

Note:

To know how to add aggregate fields to a subform, click here.
You can add formula fields to the subform. However, you can choose only the fields in the subform in your formula expression. Click here to know more about the formula fields.
You can create 2 subforms per module in the Enterprise edition and 5 subforms per module in Ultimate edition.

The maximum number of subform fields you can add in a layout is 8.
The maximum number of entries across all subforms on an aggregate is 200.

2. When to choose a related list?

A record usually contains extra information such as notes, attachments, and data related to other modules (linked via lookup/multi-select lookup fields) such as related tasks, calls, products etc.These modules are categorized as related lists, and the records in each of these related lists are called related records. To know more about related lists, refer to Kaizen #48 - Related Lists and Related Records #API.

Let us try to solve the same business scenario as above using related lists.

The system lists all the related records (child) under a record (parent) based on the value in the lookup/multi-select lookup fields in the child records.

When you link an account while adding a contact, it will be directly displayed in the respective account's related list. You can show/hide the fields that are displayed in the related list based on your business needs. However, you cannot add additional fields as in subforms.

2a. Reasons why related list is not the best choice for this case:

You cannot add an aggregate field that calculates the stakeholder share.
You cannot add any formula field.
The related list data is auto-populated based on the value in the lookup/multi-select lookup field.

2b. Business case for a related list

Consider a scenario where you need to view all the products that a contact is interested in. You can have a contact multi-select lookup in the products module. As and when you add product records with related contacts, it will be listed as related records in the respective contacts. This way you need not switch between modules to view the related records.

3. Comparing subforms and related lists

Here is a comparison between the subforms and related lists.

Subforms	Related lists
Primarily used to organize data in a record based on your business needs.	Primarily used to perceive parent-child/one-to-many relationships between records.
Allows you to add new fields (both normal and aggregate).	You can only display/hide the fields of the child record.
You cannot configure workflow rules based on subform fields (except aggregate fields)	You can configure workflow rules based on related lists.
Subforms are layout-specific.	Related lists remain the same for all the layouts in a module.
Subforms not available in Activities, Pricebooks and Purchase Orders, Sales Orders, Invoices and Quotes	The system creates related records when you add values to lookup/multi-select lookup fields. It is available in all the modules except Activities.
While converting a lead or a quote, fields used in a subform will not be converted.	While converting a lead or a quote, the related list data will be retained in the converted record.

We hope you found this post useful. Let us know your thoughts in the comment section or reach us out at support@zohocrm.com.

Cheers!

New to Zoho LandingPage?

Access Zoho LandingPage

Zoho LandingPage Resources

New to Zoho Survey?

Access Zoho Survey

Latest Feature Updates

Explore our Pricing & Plans

Zoho Survey Resources

Android Mobile Surveys

Insurvey Blogs

Insight Blogs

Tips & Tricks

New to Zoho CRM Plus?

Deliver unforgettable customer experiences

ACCESS ZOHO CRM PLUS

New to Zoho CRM Plus?

Deliver unforgettable customer experiences

ACCESS ZOHO CRM PLUS

New to Zoho Marketing Plus?

Everything you need to run your marketing

ACCESS ZOHO MARKETING PLUS

New to Zoho Marketing Plus?

Everything you need to run your marketing

ACCESS ZOHO MARKETING PLUS

New to Bigin?

Signup Now

Access Bigin

Latest Feature Updates

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Tout forum

France ZUGs

Zoho SalesIQ Resources

Sticky Posts
Extension pointers for integrating Zoho CRM with Zoho products #8: Upload and manage Zoho Workdrive folders and files from within Zoho CRM
Keeping records on your customers and business prospects is essential for tracking data, conducting follow-ups, and running a business smoothly. When you use two separate applications, and store relevant data in each, checking and tracking data becomes
Extension pointers: Handle cases with personalized solutions using custom actions
In our last post, we detailed the steps involved in creating a custom action and the workflow from the developer and end user's side. Now let's look at a working example of how we can create a custom action and implement it in a Zoho CRM account to make
Extension pointers - Simple yet significant pointers #13: On change of field value for CRM variables
CRM variables provide global access to a variable across an entire extension. They also help in the storage of user-specific data provided by the user at the time of installation, which can later be fetched to perform data functionalities. Additionally,
Extension pointers: Extend end-user benefits and allow personalization by implementing extensions with custom actions
From our earlier post on custom actions, we know that we can create templated actions, share them with end users, and allow them to reuse those actions to achieve personalized outcomes. In this post, we'll look at how custom actions make it easy for users
Extension pointers - Simple yet significant pointers #12: Functions for Zoho CRM extensions
Functions are essential in achieving logical functionality for an extension. You can easily code your functions in Deluge using drag-and-drop tools to meet your requirements. How to create functions for Zoho CRM extensions in Sigma Go to Sigma and select