fix(plugin-import-export): export relationship fields natively for JSON format#17480
Open
nathanlentz wants to merge 2 commits into
Open
fix(plugin-import-export): export relationship fields natively for JSON format#17480nathanlentz wants to merge 2 commits into
nathanlentz wants to merge 2 commits into
Conversation
…ON format hasMany and polymorphic relationship fields were flattened into field_N_id / field_N_relationTo sibling keys with the field itself set to null, regardless of export format. That flattening exists to support CSV's flat-column format, but getExportFieldFunctions.ts applied it unconditionally to JSON exports too. CSV import already reverses this via unflattenObject, but the JSON import path never did, so importing a collection's own JSON export silently dropped every hasMany and polymorphic relationship. Since JSON can hold these values natively, the export hooks now check format and skip the flattening for JSON, returning the relationship as-is instead — an id, an array of ids, or relationTo/value pairs. CSV behavior is unchanged.
nathanlentz
force-pushed
the
fix/plugin-import-export-json-relationships
branch
from
July 24, 2026 19:10
1720de5 to
d89f73f
Compare
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JSON exports of hasMany and polymorphic relationship fields now return their native value (an id, array of ids, or
{ relationTo, value }) instead of being flattened intofield_N_idcolumns with the field nulled out.[ { "id": 2, "name": "the wall", "description": "the north remembers", "events": null, "updatedAt": "2026-07-24T18:03:33.856Z", "createdAt": "2026-07-24T18:03:33.856Z", "events_0_id": 1, "events_1_id": 2 } ]That flattening only makes sense for CSV, but ran unconditionally for JSON too (#17110). JSON import never reversed it, so re-importing a collection's own JSON export silently dropped every hasMany/polymorphic relationship.
Testing
monomorphic,single-polymorphic, andhasMany-polymorphicrelationships