hasOne relationship dropdown not populating correctly in a repeatable component

[gmoigneu]

Bug report

Required System information

• Node.js version: v20.17.0
• NPM version: yarn/1.22.22
• Strapi version: 5.0.1
• Database: Postgres
• Operating system: MacOS Sequoia
• Is your project Javascript or Typescript: TS

Describe the bug

When adding or edting a repeatable component that has a hasOne relation, the dropdown for that relationship is empty at first. You have to Save the type for the dropdown to populate.

Sometimes it is required to save multiple times. Some other times, some entities are not in the list and you need to Save again so they appear.

The problem appears on all relations no matter the type in the project. Tested on a blank new project as well.

Strapi generates a SQL error:

[2024-09-28 08:47:10.026] error: select "t0".*, "t0"."id" from "public"."components_pages_icon_text_blocks" as "t0" where ("t0"."id" = $1) limit $2 - invalid input syntax for type integer: "kutz88nv52j0tus2p3ajodn2"
error: select "t0".*, "t0"."id" from "public"."components_pages_icon_text_blocks" as "t0" where ("t0"."id" = $1) limit $2 - invalid input syntax for type integer: "kutz88nv52j0tus2p3ajodn2"
    at Parser.parseErrorMessage (/Users/nls/projects/arkea-rebuild/backend/node_modules/pg-protocol/src/parser.ts:368:69)
    at Parser.handlePacket (/Users/nls/projects/arkea-rebuild/backend/node_modules/pg-protocol/src/parser.ts:187:21)
    at Parser.parse (/Users/nls/projects/arkea-rebuild/backend/node_modules/pg-protocol/src/parser.ts:102:30)
    at Socket.<anonymous> (/Users/nls/projects/arkea-rebuild/backend/node_modules/pg-protocol/src/index.ts:7:48)
    at Socket.emit (node:events:519:28)
    at Socket.emit (node:domain:488:12)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)

It actually tries to find the component (IconTextBlock) instance by document ID instead of integer ID.

Steps to reproduce the behavior

1. Edit a dynamic zone with a repeatable component with a hasOne relation
2. Add an instance of the component
3. Try to select the related entity, the dropdown is empty
4. Save
5. Now the dropdown is populated

Expected behavior

The relation dropdown should be populated with all published entities by default.

Screenshots

Code snippets

N/A

Additional context

N/A

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/relations-not-showing-in-the-admin-ui/47453/2

[Marc-Roig]

Hey! I was not able to replicate this issue anymore, so it looks like its fixed. Could you confirm this is the case?

[github-actions]

This is a templated message

Hello @gmoigneu,

Thank you for reporting this bug, however we are unable to reproduce the issue you described given the information we have on hand. Can you please create a fresh project that you are able to reproduce the issue in, provide clear steps to reproduce this issue, and either upload this fresh project to a new GitHub repo or compress it into a .zip and upload it on this issue?

We would greatly appreciate your assistance with this, by working in a fresh project it will cut out any possible variables that might be unrelated.
Please note that issues labeled with status: can not reproduce will be closed in 14 days if there is no activity.

Thank you!