`disableListFilter` does not work for nested fields in Array fields

[Exia081]

Describe the Bug

disableListFilter does not work for nested fields in Array fields

🐛 Bug Report

Description

The disableListFilter admin property does not take effect when applied to nested fields within Array fields. Despite setting disableListFilter: true, these fields still appear in the list view filter options.

Expected Behavior

When disableListFilter: true is set on a field nested within an Array field, that field should not appear in the list view filter dropdown options.

Actual Behavior

The disableListFilter: true setting is ignored for nested fields within Array fields, and these fields still appear in the filter options in the list view.

Steps to Reproduce

1. Create a collection with an Array field containing nested fields
2. Set disableListFilter: true on one or more nested fields within the array
3. Navigate to the collection's list view in the admin panel
4. Click on the "Filter" dropdown
5. Observe that the nested fields with disableListFilter: true still appear in the filter options

Code Example

export const Question: CollectionConfig = {
  slug: 'questions',
  fields: [
    {
      name: 'options',
      type: 'array',
      fields: [
        {
          name: 'id',
          type: 'text',
          admin: {
            disableListFilter: true, // This should prevent the field from appearing in filters
          },
        },
        {
          name: 'description',
          type: 'text',
          admin: {
            disableListFilter: true, // This should also be hidden from filters
          },
        },
        // ... other fields
      ],
    },
  ],
}

Environment

• Payload version: 3.44.0
• Node.js version: v22.14.0
• Database: PostgreSQL
• Operating System: macOS

Additional Context

This issue appears to be related to how Array fields handle admin properties for their nested fields. Similar issues have been reported for other admin properties like showHiddenFields not working properly with nested fields (see #408).

Workarounds Attempted

1. Using hidden: true instead - this works but completely hides the field rather than just removing it from filters
2. Using condition: () => false - this also hides the field completely
3. Moving the field outside of the array - this makes disableListFilter work correctly

Possible Related Issues

• Local API showHiddenFields does not work with nested fields #408 - Local API showHiddenFields does not work with nested fields
• Add support for virtual fields nested in arrays / blocks #12932 - Add support for virtual fields nested in arrays / blocks

Suggested Fix

The issue likely stems from the Array field's rendering logic not properly inheriting or applying admin configurations for nested fields. The admin properties should be respected for all nested fields within Arrays, Blocks, and other container field types.

Link to the code that reproduces this issue

pnpm run devsafe

Reproduction Steps

Steps to Reproduce

1. Create a collection with an Array field containing nested fields
2. Set disableListFilter: true on one or more nested fields within the array
3. Navigate to the collection's list view in the admin panel
4. Click on the "Filter" dropdown
5. Observe that the nested fields with disableListFilter: true still appear in the filter options

Which area(s) are affected? (Select all that apply)

area: ui

Environment Info

### Environment
- **Payload version**: 3.44.0
- **Node.js version**: v22.14.0
- **Database**: PostgreSQL
- **Operating System**: macOS

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[PatrikKozak]

Hey @Exia081 - thanks for bringing this up!

I just tested it out and I believe this might be working as intended.

The Options > ID field you're seeing in the filter dropdown is likely referring to the internal _id assigned to each item in the options array, rather than your nested id field.

With your example config:

fields: [
   {
     name: 'options',
     type: 'array',
     fields: [
       {
         name: 'id',
         type: 'text',
         admin: {
           disableListFilter: true, // This should prevent the field from appearing in filters
         },
       },
     ],
   },
 ],

It can definitely look like the nested id is being included in the filter options, but if you try changing the nested field’s name to something like title, you'll see that it doesn’t appear in the filter dropdown as expected.

Also, if you set disableListFilter: false, you’ll notice a second Options > Id field show up, which confirms the difference.

Would you mind giving that a try on your end and letting me know if that lines up with what you’re seeing?

Thanks again!