Zoho Creator does not currently provide native multi-step form functionality. For applications with a large number of fields, a common requirement is to split data collection into manageable sections while maintaining a single application record.

In this implementation, the application contained more than 170 fields distributed across multiple business areas, with additional fields expected over time. The completed application also triggered several API integrations that depended on the submitted data.

Single Form Approach

The initial implementation used a single Zoho Creator form.

A step-by-step experience was simulated using:

• Radio buttons for section navigation

• A hidden field to track the active section

• Show/Hide workflows to control field visibility

Each section was represented by a value in the hidden field. When the value changed, workflows displayed the relevant fields and hid the remaining fields.

This approach kept all data in a single record and allowed existing workflows and integrations to continue operating without modification.

Challenges as the Form Grew

As the form expanded, maintenance became increasingly difficult due to:

• Large numbers of visibility rules

• Section-specific workflows

• Cross-field dependencies

• Data population logic

• Additional validation requirements

Although functional, managing a form containing hundreds of fields became increasingly complex.

Stateless Forms Evaluation

An alternative considered was splitting the application into multiple stateless forms.

This would have allowed each section to manage its own:

• Fields

• Validations

• Workflows

However, the application required file uploads and image uploads, making stateless forms unsuitable for this implementation.

Implemented Architecture

The final solution retained the Main Application form as the master record and introduced multiple standard forms for individual sections.

Structure

• One Main Application Form

• Multiple Section Forms

• Shared Hidden Identifier

The hidden identifier links all section forms to the same application.

Each section form manages its own:

• Fields

• Validation rules

• Workflows

Data Flow

Step 1: Application Creation

The first section creates the application record and generates the unique identifier used throughout the process.

Step 2: Section Completion

Users complete each section through its dedicated form.

Step 3: Data Synchronization

When the first section is submitted, a record is created in the Main Application form.

For all subsequent sections, the existing Main Application record is updated rather than creating new records. This ensures that all information remains centralized within a single application record.

Step 4: Final Processing

Once all sections are completed, the Main Application record contains the complete dataset required for downstream processing.

API integrations and other business workflows are executed from the Main Application record.

Navigation

Navigation between sections is handled through Next and Back controls.

Next

The Next action:

• Validates the current section

• Saves the section data

• Synchronizes information with the Main Application record

• Opens the next section

• Opens the existing record in edit mode if data has already been entered for that section

Back

The Back action:

• Returns the user to a previously completed section

• Opens the corresponding record in edit mode

• Preserves previously entered information

• Prevents duplicate record creation

The navigation logic is reusable across all section forms.

The implementation details of the Back button are covered separately here: Back Button

Result

This architecture provides:

• Independent section forms

• Section-level validation and workflows

• Support for file and image uploads

• A single master application record

• Compatibility with existing integrations and reporting

Users interact with a guided multi-step process, while all application data remains centralized in a single record.

Has anyone implemented multi-step forms differently in Zoho Creator?

I'd be interested to hear other approaches, especially for applications with large numbers of fields, complex validations, or integration-heavy workflows.