forms submissions form select is disabled on multitenant example

[dominic-sylvester]

Describe the Bug.

I added the form submission plugin into the multitenant example and the form mt works but the form submissions does not allow to select the form from the form dropdown.

I have regenerated the importmap, schema and types.

Recap

• Forms multitenant works (only tenant forms show by tenant)
• Form Submissions does not allow to select form from the tenant (for any tenant)

Reproduction Steps

initialize the multitenant example

Add formbuilderplugin to config
Add forms and form-submissions to multitenant collections
Create form within a tenant
Create a form submission
Form select for the tenant is disabled.

Environment Info

Binaries:
  Node: 22.11.0
  npm: 11.1.0
  Yarn: N/A
  pnpm: 9.14.2
Relevant Packages:
  payload: 3.20.0
  next: 15.1.6
  @payloadcms/db-mongodb: 3.20.0
  @payloadcms/graphql: 3.20.0
  @payloadcms/next/utilities: 3.20.0
  @payloadcms/plugin-form-builder: 3.20.0
  @payloadcms/richtext-lexical: 3.20.0
  @payloadcms/translations: 3.20.0
  @payloadcms/ui/shared: 3.20.0
  react: 19.0.0
  react-dom: 19.0.0

[JarrodMFlesch]

Can you expand on what you mean here:

Form Submissions does not allow to select form from the tenant (for any tenant)

Or maybe post a screen recording of what you are meaning?

[jacobsfletch]

@dominic-sylvester the form builder plugin forces all fields of the form submissions collection to be read-only, and also prevents updates to these documents via access control. This is by design. This is to protect the form submission data from changing after it's been created. For example, anyone should be able to create a form submission, such as from a public-facing website, but no one should be able to update a submission after its been submitted. This would cause discrepancies between what the user actually submitted vs. what the editor changed it to be.

Is there a reason you need to edit these fields? If absolutely necessary, the plugin allows you to override any of the default fields that this plugin sets up.

[mikecebul]

@dominic-sylvester the form builder plugin forces all fields of the form submissions collection to be read-only, and also prevents updates to these documents via access control. This is by design.

I just saw what he meant today. A read-only field should not block the admin from creating a row in a collection, but it does here. I can't even figure out how to check if (operation === 'create') to disable it. Only workaround I found to allow creating submissions from the admin panel is overriding readOnly: false and losing protection after it's created.

Any ideas besides creating a whole component from scratch?

[jacobsfletch]

@mikecebul I would agree with this. Thanks for the clarification here. I'm going to re-open this issue as I have a fix for this queued up in #11222.