Multi-Select Lookup fields in Zoho CRM let a single record link to multiple records in another module simultaneously — here's what you need to know about setting them up and their current limitations.
Why this matters
When your business process requires associating one record with several related records at once — for example, linking a Contact to multiple Deals or a custom module to several related entries — a standard single-value Lookup field falls short. Multi-Select Lookup fields solve this by allowing many-to-many relationships between modules. Understanding both how to use them and where they currently fall short will save you significant rework down the line.
Step-by-step
Step 1. Confirm you are working in the Zoho CRM web (desktop) interface. Multi-Select Lookup fields are available through the browser-based version of Zoho CRM. Be aware from the outset that these fields do not currently appear in the Zoho CRM mobile app, which is a known platform limitation you will need to plan around. [1]
Step 2. Navigate to Setup → Customization → Modules and Fields and select the module where you want to add the Multi-Select Lookup. This is the module that will hold the "many" side of the relationship.
Step 3. In the field editor for that module, drag a new field onto the layout. Look for the Multi-Select Lookup field type in the field palette. This field type creates a relationship that allows a record to reference multiple records from a connected module simultaneously. [6]
Step 4. Configure the field by giving it a name and selecting the target module — the module whose records you want to be selectable. For example, if you are building a custom module and want to associate it with Deals, you would select the Deals module as the lookup target. The API will reflect this as a custom multi-select lookup (for instance, a field like Associated_Deal in API responses). [6]
Step 5. Save the layout. Once saved, the field will appear on the record detail view in the desktop browser. Users can then open a record, click into the Multi-Select Lookup field, and select multiple related records from the target module.
Step 6. If you are working with the Zoho CRM API (v8), be aware that Multi-Select Lookup fields appear in the $hasmore response object alongside subforms. When retrieving records via the Get Records endpoint, the API response will include a $hasmore key for your custom multi-select lookup field, indicating whether additional associated records exist beyond the default page of results. [6]
Step 7. For users who need to interact with Multi-Select Lookup data on the go, the current workaround is to use the desktop browser version on a mobile device rather than the native Zoho CRM mobile app, since the mobile app does not render these fields. This is an acknowledged gap in the platform. [1]
Common pitfalls
- Mobile app invisibility: This is the most impactful limitation. If your team relies on the Zoho CRM mobile app as their primary interface — particularly for field work — Multi-Select Lookup fields will simply not appear. Users working in industries like construction, field services, or any role requiring on-site data entry will find this a significant constraint. Plan your module architecture with this in mind before committing to Multi-Select Lookups as a core part of your workflow. [1]
- Rework risk: Building your CRM customisation around workarounds for missing mobile support means you may need to restructure layouts and retrain users if and when Zoho adds mobile support for this field type. Factor this into your implementation timeline. [1]
- API pagination for related records: When fetching records through the API, the
$has_moreflag for a Multi-Select Lookup field signals that not all associated records were returned in a single response. If you are building integrations or automations that read these fields, ensure your code handles pagination correctly to avoid missing linked records. [6]
- Conditional layouts: If you are planning to use conditional layouts driven by a Multi-Select field, note that this is a separate field type (Multi-Select picklist, not Multi-Select Lookup) and the two behave differently in layout rules. [2]
What to check
- Verify field visibility on desktop: After saving the layout, open a test record in the browser and confirm the Multi-Select Lookup field appears and allows selection of multiple records from the target module.
- Confirm mobile impact on your team: Check whether any of your users rely on the Zoho CRM mobile app as their primary interface, and communicate the limitation clearly before go-live. [1]
- Test API responses if integrating: If you have any Deluge functions, workflows, or third-party integrations reading this module, retrieve a sample record via the API and confirm the
$has_morekey is handled correctly in your logic. [6]
---
*Beam Help is an independent expert support resource for Zoho products and is not official Zoho support. For platform roadmap questions, contact Zoho directly.*