payloadcms / payloadcms/payload

Extend formBuilderPlugin fields: not persist data

Open
#7,787 5 comments 2 reactions 1 assignee View on GitHub

@paulpopus is already working on this.

Since Feb 9, 2026.

Bug stale
Dominant language
TypeScript
Stars
44.8k
Forks
4.2k
Avg merge
2d 21h
Merged PRs (30d)
53

Description

Link to reproduction
Payload Version

3.0.0-beta.86

Node Version

v20

Next.js Version

15.0.0-canary.121

Describe the Bug

If I add a custom field in the plugin configuration, it displays correctly in the admin UI but the data is not persisted.
If I add the "slug" property the data is persisted but there is a typescript error because is missing in the interface FieldConfig.

Reproduction Steps
  1. Declare the custom field
import { fields, formBuilderPlugin } from "@payloadcms/plugin-form-builder";
import { Block } from "payload";

export const formBuilderPluginConfig = formBuilderPlugin({
    redirectRelationships: ["pages"],
    fields: {
        hidden: {
            // slug: "hidden", // <- With this prop works
            labels: {
                singular: 'Hidden',
                plural: 'Hidden'
            },
            fields: [
                ...(fields.text as Block).fields
                // Other fields
            ]
        }
    },
})
  1. Open the Admin UI to add the custom field
  2. Save
  3. Data is not persisted
Adapters and Plugins
"@payloadcms/db-mongodb": "beta",     "@payloadcms/email-nodemailer": "beta",     "@payloadcms/next": "beta",     "@payloadcms/plugin-cloud-storage": "beta",     "@payloadcms/plugin-form-builder": "beta",     "@payloadcms/plugin-nested-docs": "beta",     "@payloadcms/plugin-seo": "beta",     "@payloadcms/richtext-lexical": "beta",     "@payloadcms/storage-s3": "beta",     "@payloadcms/ui": "beta",

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.