What you'll build
The outcome
You'll be able to open any record from a Table, Kanban, Gallery, or List block and edit it in a large, standalone view that behaves like the published form itself, not a stripped-down panel.
What's new vs. what stays the same
Formaloo has always let you edit a record from the Edit Row Sidebar, and that sidebar isn't going anywhere. It still works exactly as it does today, including which fields it can show. What's new is a second way to open the same record: the full-page view. It runs the form's actual logic, resolves answer piping live, and renders the sections, rich text, images, and other content fields the sidebar has never displayed. Both views update the same record, not separate copies, and you decide per data block which one your team sees.
When to use this
Your form uses conditional logic to show or hide fields, and editors currently can't see those rules play out while updating a record from the sidebar.
A calculated or scored field needs to recalculate the moment someone changes an answer during review, not just at the original submission.
The record carries instructions, section descriptions, or reference images the respondent saw, and your reviewers need that same context while editing.
A single record has enough fields, linked rows, or content that the sidebar's narrow panel makes editing slow to navigate.
You want record editing to match the Form UI closely enough that training new reviewers takes less explaining.
When to use the sidebar vs. the full-page view
Sidebar: quick, low-friction edits, flipping a status, correcting a typo, updating a field or two without needing the rest of the form's logic to run.
Full page: the edit depends on the form itself, anything conditional, calculated, piped, or explained with text and images belongs here.
You can turn on both
You don't have to choose only one. Turn both on for a data block and let the person editing decide which one fits the moment. Neither record permissions nor field visibility change based on which one they pick.
Where it works
Table, Kanban, Gallery, and List blocks, wherever the Edit Row Sidebar is already available today.
Both the dashboard and any portal built for internal or external reviewers, under the same access rules in both places.
Choosing which editing experience is available
1. Open the block's settings: While in Edit mode, open the settings for the Table, Kanban, Gallery, or List block showing your records.
2. Find Record editing: Inside the block's settings, locate the Record editing section. It lists two separate toggles: Edit row sidebar and Full-page edit row.
3. Turn on what you want available: Leave Edit row sidebar on for the familiar panel, turn on Full-page edit row to add the new view, or switch both on so people can choose.
Note: At least one of the two toggles has to stay on while editing is allowed for the block. Formaloo won't let you turn both off at once. New and existing blocks keep today's behavior, sidebar only, until you turn Full-page edit row on yourself. Turning on the full-page view doesn't change who can edit a record or which fields they can see; it only changes the window they edit it in.
Opening a record in full page
If only Full-page edit row is on: clicking a record opens it straight into the full-page view.
If only Edit row sidebar is on: nothing changes. You get the sidebar exactly as before.
If both are on: the main click still opens the sidebar, and an Open in Full Page option sits in the record's menu for anyone who wants the larger view instead. If you've already opened the sidebar, an expand option there switches you into the full-page view and carries over anything you've already typed, so an edit in progress isn't lost.
The layout
The full-page view opens as a large window over your data block (a compact, full-screen view on phones and tablets). A sticky header shows the record's title and a close action; a sticky footer keeps Save, Reset, and the record's other actions reachable no matter how far you've scrolled. Below the header, the form's fields appear in their configured order on one side, with status, tags, assignee, generated PDFs, and similar record details grouped on the other.
Content fields show up here too
Because the full-page view renders the form itself, it also shows section headings, descriptions, rich text, images, and video exactly as they're configured, elements the sidebar skips entirely. These stay display-only; adding support for them here doesn't turn them into editable fields.
Field visibility carries over automatically
Where it's controlled
Field visibility isn't a separate setting for this new view. While in Edit mode, open a Table block's Options and go to Columns to mark fields as visible or hidden, the same Column settings you'd use to clean up the table itself.
📖 See how to view your form responses for where Column settings lives and how visible and hidden columns work.
One list, not two
Whichever fields you've hidden there stay hidden in both the Edit Row Sidebar and the full-page view. There's one visibility list behind both editors, not two to maintain.
💡 Want internal fields, like status, assignee, or scores, invisible to the person filling out the form? Admin-only fields are a separate, related mechanism: hidden columns keep a field out of your editors' view, while admin-only keeps it out of the respondent's view. An admin-only field stays admin-only in both editors too.
How form logic, calculations, and answer piping run
Logic evaluates the moment you open a record
When a record opens in the full-page view, Formaloo evaluates the form's logic against the record's saved values immediately, before anyone touches a field. Conditions that should already be showing or hiding a field, or that feed a calculated value, are applied right away rather than waiting for the first edit.
💡 Want your form to show, hide, or require fields based on what someone just answered? This is the foundational guide to logic in Formaloo: what it is, and the difference between logic and calculation.
Logic keeps running as you edit
From there it runs live. Change a field that a rule depends on, and the dependent field, calculation, or piped text updates on the spot, the same way it would for someone filling out the form for the first time. Also Answer piping updates the same way.
💡 Want to pull a submitter's own answers into later questions or content? Answer piping is how Formaloo passes data using @field_id variables, and it resolves the same way here, in titles, descriptions, sections, and rich text, updating live as the referenced field changes.
Go To and Jump don't run here
One logic action is deliberately left out: a rule that jumps to another page or step does nothing here. Any other actions in that same rule still run; only the navigation part is skipped, since there's no "next page" to jump to inside a single editing window.
Multi-page forms show as one scrollable view
The same idea applies to forms that are normally shown one question at a time. The full-page view doesn't recreate that flow either: it lays the whole form out as a classic, single scrollable view, with each page break shown as a labeled divider instead of a separate screen to click through.
Permissions and visibility always win
Logic can change what's visible, but it never gets the final word. If a field is already hidden from the editor, whether through hidden columns or because it's admin-only, a logic rule that says to show it is ignored and the field stays hidden. Access and admin-configured visibility always come before conditional logic, in both editors.
Nothing saves until you click Save
Nothing is saved just from opening or closing the window. A record only updates when you click Save, at which point logic-driven changes are validated and persisted the same way a manual edit would be.
A worked example
The setup
Take a patient intake form with Insurance type, Policy number, Group number, Visit type, and a calculated Estimated copay field. The form's logic shows Policy number and Group number only when Insurance type is Private insurance, and hides them for Self-pay or Medicaid; Estimated copay is calculated from Visit type and Insurance type.
Editing the record
Open an existing patient record in the full-page view and that logic is already applied: if the record says Self-pay, Policy number and Group number stay hidden, and Estimated copay shows the figure already calculated from the saved visit type. Change Insurance type to Private insurance, and Policy number and Group number appear immediately, no save and reopen needed. Adjust Visit type, and Estimated copay recalculates on the spot. Saving the record persists the new insurance type, the now-visible policy details, and the recalculated copay together, as one update.
What's next
Go deeper on logic Once reviewers are editing records inside the full form's rules, it's worth knowing the full range of what those rules can do beyond show and hide. → How to add advanced logic to your form
Get comfortable with answer piping The full-page view leans on piping for titles, descriptions, and content, so understanding the full variable syntax pays off quickly. → How to use answer piping in Formaloo
Find records faster before you open them With more context available inside each record, it also helps to narrow down which ones you open in the first place. → How to sort and filter your submissions data
Ready-to-use templates
Don't build this from scratch. We've already put it together for you.
Patient intake and consent workflow for healthcare clinics: an intake form with conditional insurance fields, close to the worked example above. Turning on Full-page edit row lets front-desk staff see the same conditional fields and calculations the patient's record already carries.
Scholarship & grant application with scoring and approval: a multi-field review workflow with calculated scores. The full-page view keeps those calculations live for reviewers adjusting scores after submission.
AI-powered job application pipeline with candidate screening: a record-heavy pipeline with linked data and screening fields. The extra room in the full-page view suits records with this much going on.
📖 Don't have a form yet? Create one in seconds with Magic Create.
Learn more how-tos
Intake forms with conditional, sensitive fields A close match for the worked example above, with its own conditional logic and front-desk review pattern. → How to build a patient intake and consent workflow for healthcare clinics
Scoring and approving applications Shows the same pattern of calculated fields updating as reviewers edit a record after the fact. → Scholarship & grant application with scoring and approval workflow
Reviewing candidates with AI-assisted screening Another record-heavy workflow where a bigger editing window, not just a sidebar, makes reviewing each entry easier. → How to build an AI-powered job application pipeline with candidate screening