Open-source grids for Salesforce
Source you assemble and keep running yourself. Each of these is free and readable; none installs as a managed package, so every upgrade, fix and dependency is yours to manage.
What they do well
- The UnofficialSF Datatable is a Flow screen component. An admin drags it onto a screen flow to show, sort, filter, search, select and inline-edit a record collection, with a row button that launches another screen flow. Rowhouse does not offer a Flow screen component.
- Configuration as Custom Metadata, in two of the three. lwc-utils keeps its grid settings, row actions and lookups in Custom Metadata types, and od-datatable keeps its record-page and Experience Cloud tables as JSON in a Custom Metadata record, so both move from sandbox to production as metadata.
- Grouping, totals and real saves in od-datatable. One level of grouping, COUNT, AVG, SUM, MAX and MIN with group totals and a grand total that recalculate as you edit, inline add, edit and delete, bulk edit, CSV export, and placement on Experience Cloud pages.
- Documentation that states its limits. The UnofficialSF Datatable publishes its 2,000-row cap and the field types it cannot edit; lwc-utils keeps a limitations page per component and a page explaining how it enforces sharing and field security.
Components you assemble, not a package you upgrade
All three are free, and their source is public under permissive licenses: BSD-3-Clause for the UnofficialSF Datatable and lwc-utils, MIT for od-datatable. None is a managed package. The UnofficialSF Datatable installs as an unlocked package after two prerequisite base packs, then needs its configuration-wizard flow activated and a permission set assigned. lwc-utils installs as an unlocked package or as source, and its row actions need a hidden Aura component on every page or in the utility bar. od-datatable has no package at all: a button deploys its source from the main branch into your org.
That shape has a cost the license price does not show. Upgrades are yours to run, dependencies are yours to track, and when a Salesforce release breaks something, help comes from a public issue tracker or from whoever on your team owns the code. The other shape is a managed package, which Rowhouse is: one versioned unit you install and later upgrade.
What each one does
The UnofficialSF Datatable is a Lightning Web Component on Salesforce’s lightning-datatable, built for Flow screens, with no record-page or app-page target. The flow supplies the records; the table sorts one column at a time, filters per column, searches, pages, selects and inline-edits, and it can show Apex-defined data that is not a Salesforce record. Its documentation caps it at 2,000 rows and warns of Apex CPU errors above that. It reads one object, with no related-object fields, and lists lookup, encrypted, time, multi-select picklist, rich text and long text area fields among those it cannot edit.
lwc-utils, by James Hou, centers on SOQL Datatable: give it a SOQL string and it becomes a list view, a related list or a screen-flow table, with inline edit, custom picklist and lookup cells, row actions that open a flow or a component in a dialog, and aggregate queries with GROUP BY. Its own limitations page says multi-column sort, column filtering and child queries are not supported, and that keyboard navigation is not supported in inline edit. The grids are Lightning Web Components; the dialogs behind them are Aura.
od-datatable, from On Duty Software Solutions, works on Flow screens, Lightning record pages and Experience Cloud pages. Beyond grouping and totals it pages, launches flows from row and bulk buttons, and refreshes on a platform event. It has no search box or end-user column filter. Its Apex enforces field-level security on read, with Security.stripInaccessible, and its documentation states that record-level sharing is off unless the admin switches it on.
Where configuration lives
lwc-utils and od-datatable keep configuration in Custom Metadata. lwc-utils defines a grid as a SOQL string in the page’s component settings, with its actions, lookups and settings in three Custom Metadata types. od-datatable’s tables outside Flow are a JSON blob, built in a flow and pasted into a Custom Metadata record. The UnofficialSF Datatable keeps its settings in the flow screen’s component attributes, part of the flow itself, and its saved column layouts as records in a custom object rather than as metadata.
Who makes each one, and what it does
| Product | Made by | License | Last release or commit | Rating or stars | Inline edit | Paste ranges | Undo |
|---|---|---|---|---|---|---|---|
| UnofficialSF Datatable | UnofficialSF | BSD-3-Clause | 2026-05-15 | 648 GitHub stars | Yes | No | No |
| lwc-utils | tsalb | BSD-3-Clause | 2021-10-09 | 397 GitHub stars | Yes | No | No |
| od-datatable | On Duty Software | MIT | 2026-08-24 | 18 GitHub stars | Yes | No | No |
Common complaints
What we read: Each project’s GitHub issues, pull requests and documentation, and the community threads about it, read on 7 October 2026.
- UnofficialSF Datatable
Issues go unanswered
Of the 362 open issues in the LightningFlowComponents repository that holds the Datatable, 133 have no comment, and the oldest open issue dates from 2018. Of the issues labelled for the Datatable, 50 are open and 41 closed.
Evidence Counted from the repository’s own issue search.
- UnofficialSF Datatable
Dates, time zones and currencies
Dates showing a day early or blank in some locales, and percentages and multi-currency values shown wrongly. Fixes have shipped (version 4.3.5 changed how dates are stored), but the issues remain open.
Evidence 7 open issues, some with ten or more comments.
- UnofficialSF Datatable
Upgrades are manual
It installs from a link, not AppExchange, and the repository publishes no releases, so nothing tells you a new version exists; UnofficialSF’s own upgrade steps are to remove the old package and install the new one.
Evidence A community thread, and the repository.
- lwc-utils
No release since October 2021
The last release and the last maintainer commit are both from 9 October 2021, and nothing in the repository says so; people are still forking it in 2026. Nine pull requests are open, including community fixes from 2021 to 2023.
Evidence The repository’s releases, commits and pull requests.
- lwc-utils
No keyboard navigation in inline edit
Its own limitations page says keyboard navigation is not supported in inline edit.
Evidence Its documentation.
- od-datatable
Record sharing is off by default
Its documentation says the component runs without sharing by default, so an admin has to change a setting before it respects record-level sharing.
Evidence Its documentation and source.
- od-datatable
No search, column filter or calculated columns
Search, conditional edit and calculated columns are open feature requests from 2025.
Evidence The project’s open issues.
What reviewers and each vendor’s own documents say, with links; counts are of the reviews we read, not of customers, and quotes are cut short. Nothing was installed or tested. Rowhouse has no reviews yet: it has not shipped.
Choose one of these when
- Every table you need sits inside a screen flow, under 2,000 rows and on one object: the UnofficialSF Datatable already does it.
- You want a rollup table on a record page from a SOQL GROUP BY, and you have a developer who will own a fork: lwc-utils.
- You need an editable related list with one level of grouping and subtotals, on a record page or an Experience Cloud page, and you are comfortable deploying source: od-datatable.
- Someone on your team will own the component after it is installed: its upgrades, its dependencies and its issue tracker.
Checked 2026-10-07; due for a re-check by 2027-04-07. These are each vendor’s own published claims; nothing was installed or tested. Something wrong? Tell us and we will correct it.
Open-source grids: questions
What do the GitHub star counts tell me?
That people starred a repository, not that they use the component. The 648 stars on UnofficialSF’s LightningFlowComponents repository cover its whole collection of Flow components, not the Datatable alone.
How recently was each one updated?
The UnofficialSF Datatable’s last release, 4.3.7, is dated 15 May 2026. od-datatable’s last release, 2.2.0, is dated 25 January 2026 and its last commit 24 August 2026. lwc-utils’ last release, 1.9.0, and its last commit are both dated 9 October 2021, and the repository is not archived.
Which of them save edits themselves?
od-datatable saves through its own Apex, and lwc-utils’ SOQL Datatable saves through Lightning Data Service. The UnofficialSF Datatable does not write: it hands edited rows back to the flow, and an Update Records element commits them.
Where does each one keep its configuration?
The UnofficialSF Datatable keeps it in the flow screen’s component attributes, with optional saved column layouts as records. lwc-utils uses a SOQL string on the page plus Custom Metadata rows, and od-datatable uses flow attributes or a JSON Custom Metadata record.
Three things you can verify without asking us
Nobody should pay per seat to edit a thousand rows.
Compare it on your own data: install it beside the grid you have, and keep both until you are sure.