Zoho CRM Case ID vs Case Number: Deep Dive for Deluge and API Integrations | Zoho Partner

Record IDs and Case Numbers in Zoho CRM: A Deep Dive for Integrations and Deluge

Anyone building integrations around the Cases module eventually asks which identifier to store. This deep dive explains the practical differences between the human-readable Case Number and the system identifiers, and gives a safe pattern for using each in Deluge functions, API calls and reports.

Note: Some details of the Cases module are legacy, implementation-specific behaviour. Field API names and identifier handling should be confirmed in your own account under Setup, then Developer Hub, then APIs, before you build anything that depends on them.

Two kinds of identifier

  • Case Number: a sequential, human-readable reference that suits customer emails, call scripts and reports.
  • Record ID: the system-generated identifier that every CRM record carries. This is the value the API expects when you fetch or update a specific record.

A safe design pattern

  1. Store the record ID in any external system as the key used for lookups and updates.
  2. Store the Case Number alongside it purely for display and for matching what customers quote.
  3. Never assume that a Case Number can be converted into a record ID by arithmetic or formatting.
  4. When a customer quotes a Case Number, search for the Case first, then use the returned record ID for everything that follows.

Illustrative Deluge sketch

The sketch below shows the shape of the logic only. Please verify the function names and the field API name in the current Deluge documentation and in your account before use.

// Step 1: find the Case by the number the customer quoted
caseNumber = "1234";
matches = zoho.crm.searchRecords("Cases", "(Case_Number:equals:" + caseNumber + ")");

// Step 2: use the record ID from the result for every later call
if(matches.size() > 0)
{
    recordId = matches.get(0).get("id");
    caseRecord = zoho.crm.getRecordById("Cases", recordId);
    info caseRecord;
}

Common pitfalls

  • Using the Case Number as a key in a spreadsheet, then losing matches when the format changes.
  • Treating record IDs as numbers in tools that round long values. Keep them as text.
  • Hard-coding a field API name copied from another account without checking it.
Need help? 1 Cloud Consultants, a Zoho Partner, can review your Deluge functions and integrations for identifier handling. Book a discovery call with 1 Cloud Consultants.