zc_NextUrl, it's possible to redirect users back to a filtered report or a direct detail view URL.
| Expected Behavior | Current Zoho Creator Behavior | User Impact |
|---|---|---|
| Click on related record → Opens record's Detail View | Possible via URL formula (HTML) or RTF workarounds | ⚠ Requires workaround setup |
| After editing → Redirect back to filtered report | Possible using dynamic zc_NextUrl |
⚠ Returns to report, not detail view |
| After editing → Return to parent's Detail View open | No URL pattern to open detail view within report context | ✗ Broken UX: Redirects to list, user must find and reopen parent record |
| Direct URL to open record's detail view | Possible, but opens as standalone page outside report | ✗ No "back" navigation, loses report context |
| Open child in popup (stay on parent) | Works for ADDING records, but not for viewing/editing existing ones | ✗ Inconsistent behavior between add vs view/edit |
| Workaround Approach | Implementation | Problems | Status |
|---|---|---|---|
| zc_NextUrl → Filtered Report | Use zc_NextUrl to redirect back to a report filtered to the parent record |
- ✓ Returns user to correct report showing parent - ✓ Report context and navigation preserved - ✗ Detail view is NOT open on return - ✗ User must click again to open detail view |
⚠ Extra click required |
| zc_NextUrl → Direct Detail View URL | Use zc_NextUrl to redirect to the parent record's direct detail view URL |
- ✓ Opens parent's detail view directly - ✗ Opens OUTSIDE report context - ✗ No "back" button or report navigation - ✗ User is stranded on isolated page |
⚠ Loses navigation context |
| URL Formula Field (Display as HTML) | Create a formula field with direct URL, set to display as HTML to render as clickable link |
- ✓ Can navigate TO the child record - ✓ Can use zc_NextUrl for return - ✗ Same limitations as above for return navigation |
⚠ Return options both flawed |
| RTF Field with On Success Code | Use Rich Text Format field populated via workflow to create clickable link |
- ✓ Can navigate TO the child record - ✓ Can use zc_NextUrl for return - ✗ Same limitations as above for return navigation - ✗ Extra workflow scripting required |
⚠ Return options both flawed |
| Replace Related Block with Embedded Report | Use a Page with an embedded/filtered report instead of native Related Block |
- Loses native Detail View layout - Requires custom Page development - More complex maintenance - Loses summary layout formatting |
⚠ Functional but high effort |
| JavaScript Widget | Build a complete custom widget to replace Related Block functionality |
- Requires significant development effort - Must rebuild all Related Block features - Maintenance overhead - May not match native styling |
✗ Overkill for basic navigation |
zc_NextUrl to this standalone URL still leaves user outside report context&view_mode=detail) that opens the detail view within report context.┌─────────────────────────────────────────────────────────────┐
│ CUSTOMER DETAIL VIEW (within Customers_Report context) │
├─────────────────────────────────────────────────────────────┤
│ Name: Acme Corporation │
│ Email: contact@acme.com [Close] ← Returns to report │
├─────────────────────────────────────────────────────────────┤
│ RELATED ORDERS [+ Add Order] │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Order # │ Date │ Amount │ Status │ Link ││
│ │ ORD-002 │ 2024-02-20 │ $3,500 │ Pending │ [Edit] ←─┼┼─ User clicks
│ └─────────────────────────────────────────────────────────┘│ existing record
└─────────────────────────────────────────────────────────────┘
│ │
│ [+ Add Order] │ [Edit] existing
▼ ▼
┌─────────────────────────┐ ┌─────────────────────────┐
│ ✓ POPUP APPEARS │ │ ✗ FULL PAGE NAVIGATION │
│ (Parent preserved!) │ │ (Context lost!) │
├─────────────────────────┤ ├─────────────────────────┤
│ New Order Form │ │ Must use zc_NextUrl │
│ [Save] [Cancel] │ │ with flawed options... │
│ │ │ │
│ ✓ Close → back to │ │ A. Filtered report │
│ parent detail view │ │ (extra click) │
│ │ │ B. Direct detail URL │
│ WHY DOESN'T THIS │ │ (no navigation) │
│ WORK FOR EDIT TOO? │ │ │
└─────────────────────────┘ └─────────────────────────┘Current behavior:
[+ Add Related Record] → Opens popup → Parent detail view preserved ✓
Requested extension:
[Click existing record to view/edit] → Opens popup → Parent detail view preserved ✓
// The infrastructure already exists - just needs to be applied to view/edit!// Proposed URL parameter - opens detail view WITHIN the report
#Report:Customers_Report?record_id=12345&view_mode=detail
// Used with zc_NextUrl for seamless return navigation
edit_url = child_edit_url + "&zc_NextUrl=" + encodeUrl(parent_detail_view_in_report_url);
// After save, user returns to parent's detail view WITH report context
// User can click "back" or close detail view to see report listingUser Experience Impact: Developers must choose between two poor experiences: (A) extra clicks to reopen detail views, or (B) stranding users on pages with no navigation back. Neither option provides the seamless round-trip navigation users expect from a modern database application.
Can this be addressed in a future update?
The popup behavior for adding related records already proves this is technically feasible—the infrastructure exists. We just need one of these two solutions to achieve Contextual Persistence:
|
1. Extend Popup to View/Edit Apply the existing "Add" popup behavior to viewing/editing records in Related Blocks |
2. URL Parameter for Detail View Add a parameter like &view_mode=detail to open detail view within report context
|
Either solution would eliminate the current friction where users lose their navigation context or require extra clicks to return to their workflow.
Community Input Requested: Has anyone found an effective workaround that maintains contextual persistence when navigating to/from related records? This has been a long-standing request across multiple community posts, and a native solution would benefit countless Creator developers.
Writer is a powerful online word processor, designed for collaborative work.