Wire fields widget to backend + basic edition

[Devessier]

Closes twentyhq/core-team-issues#2215
Closes twentyhq/core-team-issues#2216
Closes twentyhq/core-team-issues#2218

Fields widget edition demo

CleanShot.2026-02-19.at.17.57.05.mp4

Dashboards still work

CleanShot.2026-02-19.at.17.58.45.mp4

[github-actions]

🚀 Preview Environment Ready!

Your preview environment is available at: http://bore.pub:6667

This environment will automatically shut down when the PR is closed or after 5 hours.

[greptile-apps]

Too many files changed for review. (136 files found, 100 file limit)

[Copilot]

Pull request overview

This PR wires the fields widget to the backend and implements basic editing functionality. It introduces a new FIELDS_WIDGET view type to support field grouping in widgets, replaces the legacy section-based configuration with view-backed field groups, and adds comprehensive CRUD operations for managing field groups and their visibility.

Changes:

• Added FIELDS_WIDGET view type support and filtering in backend view services
• Implemented field group management with draft/persisted state and optimistic updates
• Replaced legacy FieldsConfiguration sections with view-based field groups
• Added utilities for dynamic relation widget injection and page layout ID resolution

Reviewed changes

Copilot reviewed 135 out of 136 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/twenty-server/src/engine/metadata-modules/view/services/view.service.ts	Added viewTypes parameter to filter views by type
packages/twenty-server/src/engine/metadata-modules/view/resolvers/view.resolver.ts	Updated resolver to accept viewTypes filter argument
packages/twenty-server/src/engine/metadata-modules/page-layout/services/*.ts	Added flatViewMaps support for widget configuration
packages/twenty-server/src/engine/metadata-modules/flat-page-layout-widget/validators/utils/validate-simple-record-page-widget-for-update.util.ts	New validator for simple record page widgets
packages/twenty-front/src/modules/views/types/ViewType.ts	Added FieldsWidget view type
packages/twenty-front/src/modules/views/utils/*.ts	Added converters for CoreViewFieldGroup and view type mapping
packages/twenty-front/src/modules/views/hooks/*.ts	Implemented CRUD hooks for view field groups
packages/twenty-front/src/modules/page-layout/widgets/fields/hooks/*.ts	Added hooks for fields widget group management with draft state
packages/twenty-front/src/modules/page-layout/utils/*.ts	Added utilities for dynamic widget handling and page layout resolution
packages/twenty-front/src/modules/page-layout/hooks/useSaveFieldsWidgetGroups.ts	Implements saving of field group changes to backend
packages/twenty-front/src/modules/users/components/MetadataProviderEffect.tsx	Split view loading into index and fields widget views

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cubic-dev-ai]

4 issues found across 136 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/twenty-front/src/modules/page-layout/hooks/useSaveFieldsWidgetGroups.ts">

<violation number="1" location="packages/twenty-front/src/modules/page-layout/hooks/useSaveFieldsWidgetGroups.ts:125">
P2: Batch deletions into a single call instead of awaiting each delete in a loop; the delete API already accepts an array and uses Promise.all. The current loop sends N sequential requests and needlessly slows saves.</violation>

<violation number="2" location="packages/twenty-front/src/modules/page-layout/hooks/useSaveFieldsWidgetGroups.ts:166">
P2: The save flow always marks the draft as persisted and returns a successful status even if one of the API calls failed (the API helpers return `{ status: 'failed' }` without throwing). This can leave local state out of sync with the server. Capture the API results and only update persisted state/return success when all requests succeed.</violation>
</file>

<file name="packages/twenty-front/src/modules/page-layout/utils/computeFieldsWidgetGroupDiff.ts">

<violation number="1" location="packages/twenty-front/src/modules/page-layout/utils/computeFieldsWidgetGroupDiff.ts:20">
P3: Repeated Array.find inside the draftGroups filter makes updatedGroups O(n²). Consider precomputing a Map of persisted groups by id to keep lookups O(1) and avoid repeated scans.</violation>
</file>

<file name="packages/twenty-front/src/modules/users/components/MetadataProviderEffect.tsx">

<violation number="1" location="packages/twenty-front/src/modules/users/components/MetadataProviderEffect.tsx:171">
P2: localAreViewsLoaded (and therefore isCurrentUserLoaded) no longer waits for the new fields widget views query. This can mark metadata as fully loaded before FIELDS_WIDGET views arrive, causing early renders with missing core views and possibly skipping the query once isCurrentUserLoaded flips to true. Track the fields widget query loading state and include it in the readiness check.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: Batch deletions into a single call instead of awaiting each delete in a loop; the delete API already accepts an array and uses Promise.all. The current loop sends N sequential requests and needlessly slows saves.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/modules/page-layout/hooks/useSaveFieldsWidgetGroups.ts, line 125:

<comment>Batch deletions into a single call instead of awaiting each delete in a loop; the delete API already accepts an array and uses Promise.all. The current loop sends N sequential requests and needlessly slows saves.</comment>

<file context>
@@ -0,0 +1,185 @@
+          }
+
+          if (deletedGroups.length > 0) {
+            for (const group of deletedGroups) {
+              await performViewFieldGroupAPIDelete([
+                { input: { id: group.id } },
</file context>

[cubic-dev-ai]

P2: The save flow always marks the draft as persisted and returns a successful status even if one of the API calls failed (the API helpers return { status: 'failed' } without throwing). This can leave local state out of sync with the server. Capture the API results and only update persisted state/return success when all requests succeed.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/modules/page-layout/hooks/useSaveFieldsWidgetGroups.ts, line 166:

<comment>The save flow always marks the draft as persisted and returns a successful status even if one of the API calls failed (the API helpers return `{ status: 'failed' }` without throwing). This can leave local state out of sync with the server. Capture the API results and only update persisted state/return success when all requests succeed.</comment>

<file context>
@@ -0,0 +1,185 @@
+          }
+        }
+
+        set(fieldsWidgetGroupsPersistedState, allDraftGroups);
+
+        await refreshAllCoreViews();
</file context>

[cubic-dev-ai]

P2: localAreViewsLoaded (and therefore isCurrentUserLoaded) no longer waits for the new fields widget views query. This can mark metadata as fully loaded before FIELDS_WIDGET views arrive, causing early renders with missing core views and possibly skipping the query once isCurrentUserLoaded flips to true. Track the fields widget query loading state and include it in the readiness check.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/modules/users/components/MetadataProviderEffect.tsx, line 171:

<comment>localAreViewsLoaded (and therefore isCurrentUserLoaded) no longer waits for the new fields widget views query. This can mark metadata as fully loaded before FIELDS_WIDGET views arrive, causing early renders with missing core views and possibly skipping the query once isCurrentUserLoaded flips to true. Track the fields widget query loading state and include it in the readiness check.</comment>

<file context>
@@ -129,6 +165,13 @@ export const MetadataProviderEffect = () => {
+      variables: { viewTypes: INDEX_VIEW_TYPES },
+    });
+
+  const { data: queryDataFieldsWidgetCoreViews } =
+    useFindFieldsWidgetCoreViewsQuery({
+      skip: shouldSkip,
</file context>

[cubic-dev-ai]

P3: Repeated Array.find inside the draftGroups filter makes updatedGroups O(n²). Consider precomputing a Map of persisted groups by id to keep lookups O(1) and avoid repeated scans.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/modules/page-layout/utils/computeFieldsWidgetGroupDiff.ts, line 20:

<comment>Repeated Array.find inside the draftGroups filter makes updatedGroups O(n²). Consider precomputing a Map of persisted groups by id to keep lookups O(1) and avoid repeated scans.</comment>

<file context>
@@ -0,0 +1,34 @@
+      return false;
+    }
+
+    const persistedGroup = persistedGroups.find((g) => g.id === draftGroup.id);
+
+    if (!isDefined(persistedGroup)) {
</file context>

[Devessier]

Identified a regression for Survey result object when flag and seeds are disabled. Investigating.

Fixed

[Weiko]

Left some comments

[Weiko]

Not sure about the naming 🤔

[Weiko]

Oh ok we already have usePerformViewFieldAPIPersist.
Alright, let's keep it consistent then!

[Weiko]

Wondering if we could batch some of those calls 🤔 (maybe not possible with the update though so probably not worth it)
Note: My concern is if one of the mutation fails you are in a broken state but that's probably the issue with the whole "save page layout" that can run many operations under the hood. Ideally we should have 1 backend call (upsertFieldsWidget or something like that) that will run behind the scene all operations within a unique transactions to avoid race conditions. We rarely do that though

[Weiko]

LGTM!

[Weiko]

Question: Do we still need all those different types / conversion? I thought this was temporary for legacy views that were in the workspace schema before being moved

[Devessier]

I will give a look

[twenty-eng-sync]

Hey @Devessier! After you've done the QA of your Pull Request, you can mark it as done here. Thank you!