A recent Quick Create client-script update stopped firing the parent form’s onChange handlers when users create a record from a lookup quick-create popup. The result: child records save but the parent page doesn’t detect the new lookup value until the user re-selects it. [1]
What it means — concrete explanation tied to the Zoho API surface
Quick Create now opens and saves the child record in a modal without propagating the lookup-change event back to the parent browser page, so Client Script onChange handlers attached to the parent field do not run automatically after a quick-create save. Client Script runs in the browser and depends on UI events to trigger your scripts, so missing events mean your existing client-side logic never executes. [1][7]
Common causes
- The Quick Create modal saves the child record but does not emit the parent lookup "change" event that Client Script relies on. [1]
- Client Script does not expose which lookup field opened the quick-create popup, so the parent script cannot infer intent when multiple lookups exist. [1]
- Your automation depends on onChange handlers (client-side) instead of server-side updates or explicit refreshes; modal saves bypass those handlers. [1][7]
- A recent platform update changed event wiring for modals; scripts that assumed parent-side events now miss triggers. [1]
How to fix it
- Short-term workaround — ask users to re-select the newly created record in the lookup field to force the parent onChange handler to run. This is the simplest immediate fix. [1]
- Prefer full-create flows for critical paths — open the full Create page (not Quick Create) when the parent logic must run immediately after creation. Use the module’s Add/Create button or a custom button that opens the creation page. [1][7]
- Move critical logic off pure onChange — implement the behavior in a parent-side onLoad or onSave flow that detects the lookup value and builds the subject/opens widgets when the parent record loads or saves. If you must react to the child creation instantly, have the child record set a marker field or call a server-side function (workflow, webhook, or custom function) to update the parent and then refresh the parent UI. [1][7]
- Programmatic refresh from child (advanced) — if you control the quick-create code (for example inside a widget), have the child call the parent via window.postMessage or an API call to update the parent and then trigger a client-side refresh. Test across supported browsers. [7]
- File a bug with Zoho Support — include a minimal reproduction: module name, exact Client Script, browser/version, sequence of clicks, and screenshots or a screen recording. Ask for either re-enabling the parent onChange trigger for quick-create saves or adding a flag on onSave to indicate the popup origin. [1]
When to escalate
If the parent behavior must run automatically and you cannot change user flow or move logic to server-side actions,