Problem with connections in components (strapi 5.0.1)

Questions and Answers
1
System Information
  • Strapi Version: 5.0.1
  • Operating System: Ubuntu
  • Database: PostgreSQL
  • Node Version: 18.20.4
  • NPM Version: 10.7.0
  • Yarn Version: 1.22.22

Hello everyone, updated strapi 5.0.1
Lost connection in components
how can this problem be solved?

[2024-09-25 19:11:47.881] error: select "t0".* from "public"."components_payment_payments" as "t0" where ("t0"."id" = $1) limit $2 - неверный синтаксис для типа integer: "n3u6beanybc7ec28zvfwlpip"
error: select "t0".* from "public"."components_payment_payments" as "t0" where ("t0"."id" = $1) limit $2 - неверный синтаксис для типа integer: "n3u6beanybc7ec28zvfwlpip"
    at Parser.parseErrorMessage (/home/dev2studio/www/MyApp/UpMon/main-server/node_modules/pg-protocol/src/parser.ts:368:69)
    at Parser.handlePacket (/home/dev2studio/www/MyApp/UpMon/main-server/node_modules/pg-protocol/src/parser.ts:187:21)
    at Parser.parse (/home/dev2studio/www/MyApp/UpMon/main-server/node_modules/pg-protocol/src/parser.ts:102:30)
    at Socket.<anonymous> (/home/dev2studio/www/MyApp/UpMon/main-server/node_modules/pg-protocol/src/index.ts:7:48)
    at Socket.emit (node:events:514:28)
    at Socket.emit (node:domain:489:12)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

image
image925×855 78 KB

2

image
image1500×349 25.4 KB

And in another revenge everything works =(

3

I have the same problem. It is observed with the “Relation” fields in the component. The error occurs when editing a table item when I click on the drop-down list

4

He passes the document ID instead of the old ID. Waiting for the update

5

Yes, that’s right. On "githubissues.com " someone writes that the update is “node.js” up to version 20.17 fixed the problem. But it didn’t help me.

6

but judging by the error, this is a problem in the code, changing the version of the node will not help since the request is not built correctly, somewhere you need to change documentID to id

7

solved the problem here “5.0.2-beta.0”