dc/datacontroller.io
6
1
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: fsedit feed post
publish / Build-and-publish (push) Successful in 13m9s
Details

Browse Source
This commit is contained in:
4gl
2026-08-09 18:00:11 +01:00
parent 14b745e2e7
commit 26304f3c73
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/feed/fsedit-paging/example.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 115 KiB

content/feed/fsedit-paging/index.md
+6 -3
View File
@@ -6,16 +6,19 @@ author: 'Data Controller'
authorLink: https://www.linkedin.com/showcase/data_controller
tags:
- Announcements
previewImg: './example.png'
---
# FSEDIT-Style Paging in the Edit Record Form
Anyone who has worked with SAS for a while will remember `PROC FSEDIT` - the full-screen editor that let you step through a dataset one observation at a time, seeing every variable for a single record laid out on screen. It was a simple, focused way to review and amend data without getting lost in a wide grid.
Anyone who has worked with SAS for a while will remember `PROC FSEDIT`. Part of the SAS/FSP (Full-Screen Product) family alongside `PROC FSVIEW` and `PROC FSBROWSE`, it was for years the standard way to edit a dataset interactively: one observation per screen, typing directly over values that committed straight to the table. That focused, one-record-at-a-time view was a simple way to amend data without getting lost in a wide grid - though edits landed immediately, with no staging or approval step in between.
Data Controller's **Edit Record** dialog brings that experience into the browser. Instead of scanning across dozens of columns in the grid, you open a single row as a form - every field labelled and stacked vertically, with dropdowns, validations and formatting applied just as they are in the main editor.
Now you can **page through your records** without leaving the form. Previous and Next arrows move you one record at a time, and a **Current row** indicator shows exactly where you are in the extract. It's the fastest way to work through a set of rows methodically - reviewing, correcting and moving on - especially for wide tables where horizontal scrolling in the grid slows you down.
You can **page through your records** without leaving the form. Previous and Next arrows move you one record at a time, and a **Current row** indicator shows exactly where you are in the extract. It's the fastest way to work through a set of rows methodically - reviewing, correcting and moving on - especially for wide tables where horizontal scrolling in the grid slows you down.
<iframe title="Forwards_Backwards_in_Edit_Record_Modal" width="560" height="315" src="https://vid.4gl.io/videos/embed/o8yzHqRqTWhYo6cgNACRkg" style="border: 0px;" allow="fullscreen" sandbox="allow-same-origin allow-scripts allow-popups allow-forms"></iframe>
As always, everything flows through the standard Data Controller workflow: your changes are staged, validated and sent for approval before they reach the target table, with a full audit trail retained.
Administrators who prefer to keep the grid-only experience can still disable the dialog with the [`DC_RESTRICT_EDITRECORD`](https://docs.datacontroller.io/dcc-options/#dc_restrict_editrecord) option.
Administrators who prefer to keep the grid-only experience can disable the dialog with the [`DC_RESTRICT_EDITRECORD`](https://docs.datacontroller.io/dcc-options/#dc_restrict_editrecord) option.