Summary
When cloning an existing Deal record in the Zoho CRM mobile app, saving the cloned record fails with the error "Deal name cannot be empty" — even though the Deal Name field is visibly populated with a valid value. The save is blocked entirely. This does not occur when creating a new Deal from scratch in the mobile app, and does not occur when cloning a Deal in the web browser.

Environment

• App: Zoho CRM Mobile (latest version as of June 2026)
• Module: Deals
• Platform: Mobile (iOS/Android)
• Browser equivalent: Works correctly — no issue

Steps to Reproduce

1. Open the Zoho CRM mobile app
2. Navigate to an existing Deal record
3. Tap the option to Clone the Deal
4. Confirm or edit the pre-populated Deal Name field (field is not empty)
5. Tap Save
6. Observe: error displays — "Deal name cannot be empty" — despite the field having a valid value

Expected Behavior
The cloned Deal saves successfully. The validation error should only fire when the Deal Name field is actually blank.

Actual Behavior
The mobile app fires a false validation error and blocks the save. The clone operation cannot be completed on mobile.

Key Observations

• Creating a new Deal from scratch in the mobile app works fine — no error
• Cloning the same Deal in the web browser works fine — no error
• This isolates the bug to the clone form state handling in the mobile client specifically
• The app is on the latest version — this is not a stale-client issue

Hypothesis
The mobile app's clone workflow pre-populates field values visually, but the Deal Name field does not properly register with the form's internal validation state — the underlying model reads it as null/empty even though the UI renders a value. This is a classic field-binding bug on the clone page that doesn't affect new-record creation because that path initializes the field differently.

Has anyone else encountered this? Zoho support has been notified, but posting here to see if there's a known workaround or if others can reproduce.