payloadcms / payloadcms/payload
Virtual polymorphic relationship field in an array is not displayed in the admin
Open
Nobody has claimed this yet.
area: ui
stale
status: needs-triage
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
Description
Describe the Bug
When a document has a virtual polymorphic field in an array (also virtual) the field value is not displayed in the admin while retrieved by the api.
Link to the code that reproduces this issue
https://github.com/Xmaster6y/bug-poly
Reproduction Steps
- Create a template and add permissions
- Create a page linked to the previously created template
- Observe the missing entity
Which area(s) are affected?
area: ui
Environment Info
Binaries:
Node: 24.8.0
npm: 11.11.0
Yarn: 1.22.22
pnpm: 10.17.0
Relevant Packages:
payload: 3.83.0
next: 16.2.3
@payloadcms/db-sqlite: 3.83.0
@payloadcms/drizzle: 3.83.0
@payloadcms/graphql: 3.83.0
@payloadcms/next/utilities: 3.83.0
@payloadcms/richtext-lexical: 3.83.0
@payloadcms/translations: 3.83.0
@payloadcms/ui/shared: 3.83.0
react: 19.2.4
react-dom: 19.2.4
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:29:54 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T8122
Available memory (MB): 16384
Available CPU cores: 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction repository and follow the template, permissions, and page setup described in the reproduction steps. Compare the admin display of the virtual polymorphic field inside the virtual array with the API response; done means the related entity is displayed in the admin as retrieved by the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100