Seamless Round-Trip Navigation for Related Blocks (Detail View)

Seamless Round-Trip Navigation for Related Blocks (Detail View)

As highlighted previously in this post (and here, here, here, and here), we still lack a fundamental capability for seamless navigation in Related Blocks. The popup that appears when adding a related record doesn't exist for viewing/editing existing records, and there's no URL pattern to open a detail view within report context. This creates unnecessary friction, and I'm hoping the Zoho team can address this in a future update.

The Core Limitation
When viewing a record's Detail View, Zoho Creator allows you to display related child records in a Related Block. Developers can create clickable links to these child records using URL formula fields (set to display as HTML) or RTF fields populated via workflow. Using zc_NextUrl, it's possible to redirect users back to a filtered report or a direct detail view URL.

The problem: Direct detail view URLs open as standalone pages outside any report context—there's no "back" button, no way to close the detail view and return to the report listing. Whether you redirect to a filtered report (requiring an extra click) or to a direct detail view URL (losing navigation context), neither option provides a seamless round-trip experience.

Note: This refers specifically to Related Blocks in Detail Views (parent-child relationships at the Report level), not Subforms within a Form.
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
Current Workarounds (All Suboptimal)
To achieve what should be native functionality, developers must resort to complex workarounds. Frustratingly, the popup behavior that works perfectly when adding a related record doesn't exist for viewing/editing existing records:
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
The Core Problem: Detail View Opens Outside Report Context
While a direct URL to a record's detail view exists, it opens as a standalone page outside of any report context. This means:
  • ✓ You CAN open a detail view directly via URL
  • ✗ But it's NOT within a report—there's no "back" button to return
  • ✗ User is stranded on an isolated page with no navigation context
  • ✗ Using zc_NextUrl to this standalone URL still leaves user outside report context
The inconsistency: When adding a related record through the detail view, Zoho Creator already opens a popup that preserves the parent context. This same behavior simply doesn't exist for viewing or editing existing records.
What's needed: Either (1) extend the popup behavior to view/edit, or (2) provide a URL parameter (e.g., &view_mode=detail) that opens the detail view within report context.

Example: The Add vs. View/Edit Inconsistency
Consider a common business scenario—viewing a Customer record with their related Orders:
Note: If the diagram below doesn't display correctly in your browser, the key point is illustrated in the comparison between [+ Add Order] (which opens a popup preserving context) vs. [Edit] existing record (which navigates away, losing 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?     │         │                         │
└─────────────────────────┘         └─────────────────────────┘

What Should Happen Instead
Proposed Solutions (Either Would Solve This):

Option 1: Extend Existing Popup Behavior to View/Edit
When adding a related record through the detail view, Zoho Creator already opens a popup that keeps the parent context intact. Simply extend this same behavior to viewing and editing existing records in the Related Block:
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!

Option 2: URL Parameter to Open Detail View Within Report Context
Provide a URL parameter that can be appended to a report URL to auto-open a specific record in its detail view context:
// 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 listing
Either solution would achieve Contextual Persistence. Option 1 may be simpler since the popup infrastructure already exists. Option 2 would provide more flexibility for developers building custom navigation flows.

Related Issues
This limitation compounds other navigation frustrations in Zoho Creator:

Real-World Impact
This limitation affects virtually any application with parent-child relationships:
  • CRM systems – Viewing a Contact's related Cases, Opportunities, or Activities
  • Project management – Viewing a Project's related Tasks or Milestones
  • Order management – Viewing a Customer's related Orders or Invoices
  • Inventory systems – Viewing a Product's related Stock Movements or Purchase Orders
  • HR applications – Viewing an Employee's related Leave Requests or Performance Reviews

User 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.


Request to Zoho Team

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.


    Nederlandse Hulpbronnen