zc_LoadIn parameter is a vital tool for opening components (forms, reports, or pages) in modal dialogs via HTML snippets, Notes, or Rich Text Fields. While powerful, this feature suffers from a critical deficiency when applied to Report components.// Standard usage in HTML Snippets or Rich Text
<a href="https://creator.zoho.com/yourapp/report-name?zc_LoadIn=dialog">Open Report</a>
// Usage with Forms and Pages (currently functional)
<a href="https://creator.zoho.com/yourapp/form-name?zc_LoadIn=dialog">Open Form</a>
<a href="https://creator.zoho.com/yourapp/page-name?zc_LoadIn=dialog">Open Page</a>| Report Scenario | Technical Conflict | UX Impact |
|---|---|---|
| Multi-Column (Wide) Reports | Viewport is narrower than the data grid | ✗ Horizontal scrollbars obscure key metrics |
| High-Volume Vertical Data | Viewport height is insufficient for pagination | ✗ Excessive vertical scrolling required |
| Drill-Down Actions | Opening a Detail View inherits the restricted parent frame size | ✗ Record details are cramped and unreadable |
zc_LoadIn generally adapt well to the default modal size. This issue specifically targets Reports, where data density and layout requirements vary drastically between use cases.
| Strategy | Implementation | Drawbacks | Verdict |
|---|---|---|---|
| Abandon Popup Mode | Open reports in a standard new browser tab/window |
- Breaks the application flow - Increases browser tab clutter - User loses context of the parent page |
✗ Degrades User Experience |
| Layout Compromise | Remove columns to fit the fixed modal width |
- Reduces data visibility - Hides critical business intelligence - Artificial limitation on report design |
✗ Sacrifices Data Value |
| Iframe Injection | Use zc_LoadIn=iframe instead of dialog |
- Loses the "overlay" modal behavior - Still lacks native dynamic resizing |
⚠ Inconsistent Behavior |
| HTML Page Recreation | Rebuild the report using HTML/Deluge on a Page |
- High development overhead - Loss of native features (Search, Filter) - Creates technical debt and maintenance drag - Styling must be manually maintained |
✗ Inefficient & Costly |
zc_LoadIn syntax that allow developers to define the modal's viewport size:
// Proposed Syntax 1: Pixel-based definitions
<a href="...?zc_LoadIn=dialog&zc_DialogWidth=1200px&zc_DialogHeight=800px">
View Report
</a>
// Proposed Syntax 2: Percentage-based definitions (Responsive)
<a href="...?zc_LoadIn=dialog&zc_DialogWidth=90%&zc_DialogHeight=90%">
View Report
</a>
// Proposed Syntax 3: Preset Classes
<a href="...?zc_LoadIn=dialog&zc_DialogSize=maximized">
View Report
</a>
// Options: small, medium, large, full-widthDeveloper Consequence: We are forced to choose between a clean UI (no popups) or a streamlined workflow (popups with bad UI). This is a choice we should not have to make in a low-code enterprise platform.
Can this enhancement be prioritized for the upcoming release roadmap?
The zc_LoadIn feature is a fantastic concept, but the fixed-dimension constraint renders it nearly unusable for complex reporting needs.
Currently, the developer experience is split:
|
1. Use zc_LoadIn Result: Fast workflow, but broken/cramped UI. |
2. Avoid zc_LoadIn Result: Clean UI, but disjointed/slow workflow. |
This creates a friction point in otherwise polished applications.
zc_DialogWidth and zc_DialogHeight (supporting px and %) to provide developers full control over the modal viewport.
Community Feedback: If you are struggling with fixed-size report popups, please comment below with your use case to help the Zoho team understand the scope of this requirement.