Fields contained in row field inside localized group don't get saved

[ivankyrpa]

Link to reproduction

https://github.com/ivankyrpa/payload-cms-beta108

Environment Info

Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 9.10.0
Relevant Packages:
  payload: 3.0.0-beta.108
  next: 15.0.0-canary.160
  @payloadcms/db-postgres: 3.0.0-beta.108
  @payloadcms/email-nodemailer: 3.0.0-beta.108
  @payloadcms/graphql: 3.0.0-beta.108
  @payloadcms/next/utilities: 3.0.0-beta.108
  @payloadcms/plugin-cloud: 3.0.0-beta.108
  @payloadcms/richtext-lexical: 3.0.0-beta.108
  @payloadcms/translations: 3.0.0-beta.108
  @payloadcms/ui/shared: 3.0.0-beta.108
  react: 19.0.0-rc-5dcb0097-20240918
  react-dom: 19.0.0-rc-5dcb0097-20240918
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:54 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 11

Describe the Bug

About

Fields inside row field that is in a localized group field don't get saved. Probably this is tied with the issue #8322.

Demo

Screen.Recording.2024-09-25.at.15.12.43.mov

Reproduction Steps

I used npx create-payload-app@beta command to create repro repo. Please use link to reproduction for the full example.

Test collection:

export const Tests: CollectionConfig = {
  slug: 'tests',
  fields: [
    {
      name: 'localizedGroup',
      type: 'group',
      localized: true,
      fields: [
        {
          type: 'row',
          fields: [
            {
              name: 'text',
              type: 'text',
            },
            ...
          ]
        }
      ]
    },

Payload config:

export default buildConfig({
  collections: [Tests, ...],
  localization: {
    defaultLocale: 'en',
    locales: ['en', 'de'],
    fallback: true,
  },
  ...
})

Adapters and Plugins

db-postgres

[HappyEmu]

I just upgraded my app to beta.110 after one of my reported bugs with respect to localization (and versions) in tandem with postgres was fixed: #7695
Since I wanted to do the switch from MongoDB to Postgres, I checked the issues for more problems related to locales and versions. This issue popped up.

TLDR: I tested this on beta.110 and this bug is still present in that version.

EDIT:
The values for the localized group fields are even included in the insert / update statement, but the respective columns are missing:

insert into "tests" ("id", "non_localized_group_text", "non_localized_group_textarea", "non_localized_group_number", "non_localized_group_checkbox", "non_localized_group_date", "nonLocalizedGroup_select", "updated_at", "created_at") values ($1, $2, $3, $4, $5, $6, $7, $8, $9) on conflict ("id") do update set "id" = $10, "non_localized_group_text" = $11, "non_localized_group_textarea" = $12, "non_localized_group_number" = $13, "non_localized_group_checkbox" = $14, "non_localized_group_date" = $15, "nonLocalizedGroup_select" = $16, "updated_at" = $17, "created_at" = $18 returning "id", "non_localized_group_text", "non_localized_group_textarea", "non_localized_group_number", "non_localized_group_checkbox", "non_localized_group_date", "nonLocalizedGroup_select", "updated_at", "created_at" -- params: [1, "asdf", "asdf", 12, true, "2024-10-01T12:00:00.000Z", "two", "2024-10-03T14:05:27.233Z", "2024-10-03T13:45:25.549Z", 1, "asdf", "asdf", 12, true, "2024-10-01T12:00:00.000Z", "two", "2024-10-03T14:05:27.233Z", "2024-10-03T13:45:25.549Z"]

Note that the second set of values ("asdf", "asdf", 12, true, 2024/10/01, "two") would be the values for the `localized_" fields.

[r1tsuu]

Thanks, this will fix it #8539.

[github-actions]

🚀 This is included in version v3.0.0-beta.111

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.