• Parent form → Can open child record for editing ✓
• Child record → Can be edited and saved ✓
• Parent form → User Input workflow does not re-trigger
• Parent form → Lookup display shows stale data
• Parent form → Dependent fields remain outdated

[ Selected Client Name     ▼ ]  [+]  [✏️]
                                 │     │
                                 │     └── Edit selected record (NEW)
                                 └──────── Add new record (existing)

// Existing User Input workflow on Client_Lookup field
// This ALREADY triggers when a record is selected
// It SHOULD also trigger when the related record is edited and saved

on user input of Client_Lookup
{
    // Populate fields based on selected client
    input.Contact_Phone = input.Client_Lookup.Phone;
    input.Contact_Email = input.Client_Lookup.Email;
    input.Billing_Address = input.Client_Lookup.Address;
}

Lookup Field Properties:
├── Allow Add New Record: ☑ Enabled
├── Allow Edit Selected Record: ☑ Enabled  ← NEW OPTION
│   └── Edit Opens In: ○ Dialog  ○ Slide-in Panel  ○ New Tab
└── On Related Record Save: ○ Refresh Lookup  ○ Custom Script  ○ No Action

• CRM/Sales workflows — Updating client contact info while creating quotes or orders
• Project management — Editing task details while logging time entries
• Inventory systems — Correcting product specifications while processing orders
• HR applications — Updating employee details while processing leave requests
• Support ticketing — Modifying customer information while handling tickets
• Data integrity — When users spot typos or outdated info but can't fix it easily, they tend to ignore it. This leads to "dirty data" accumulating simply because the "cost" of fixing it (navigating away, losing context) is too high
• Any parent-child data relationship — Where child record corrections are discovered during parent record creation

User Experience Impact: Users are forced to choose between completing their current task with stale/incorrect related data, or abandoning their work to fix the related record. This friction compounds across every data entry session, significantly impacting productivity.

Can this be addressed in a future update?

The current implementation forces users to choose between:

We shouldn't have to make this choice—lookup fields should support both adding AND editing related records.

Community Input Requested: Has anyone else encountered this limitation or developed a more elegant workaround? I'd particularly love to hear from anyone who has implemented a JavaScript Widget solution and whether the development overhead was justified.

• Primary: Understand Lookup Fields - Zoho Creator Help
• Related: Functionality-based URLs (Editing Records via Record ID)
• Related: openUrl() - Deluge Documentation
• Related: JavaScript Widgets in Creator

• Manually edit preexisting entry in lookup field
• Change subform to vertical layout (edit icon for lookups suggested 7 years ago—acknowledged by Zoho but never implemented)