I don’t think we can nest group fields in another group field.

dangerous057 months ago

7

• 

  tyteen4a03last year

  Don't use groups is my advice

  
  
  

  The generated UI is not as nice

  
  
  

  I don't remember if filtering has improved now

• 

  tylandavis

  last year

  Hey

  @789268703774375986

  , you actually can do this! Here's an example:

  
  
  

  fields: [
    {
      name: 'topGroup',
      label: 'Top Group',
      type: 'group',
      fields: [
        {
          name: 'field1',
          label: 'Field 1',
          type: 'text',
        },
        {
          name: 'nestedGroup',
          label: 'Nested Group',
          type: 'group',
          fields: [
            {
              name: 'field2',
              label: 'Field 2',
              type: 'text',
            },
          ],
        },
      ],
    },
  ]

  
  
  

  UI field types don't have values, they are just for adding in custom React components. If you want to store value with a custom component, start with a field type that stores value such as

  text

  or

  number

  , whatever the type of data you want to save, and then use

  admin.components

  to customize it.
• 

  rufellalast year

  Always try to reload the express server first 😛

• 

  oatmocha8 months ago

  Hi sorry for following up on an old post, were there any specific reasons or disadvantages to using groups? Will it complicate my config to nest fields within groups?

• 

  simka09978 months ago

  Don't use groups is my advice

  isn't good advice in my opinion. I mean the use cases of Payload vary so much...

  
  
  

  You do "pay a price" for using them. For example: Payload doesn't allow to display nested fields in the list view atm (V2, not sure about V3).

  
  
  

  You can still create a custom list view or add the column yourself, it's just a little more work.

• 

  anders22928 months ago

  Filtering works in v3 beta, but lisview does not yet.