@winston0410 Did deleting the yarn.lock fix your issue?
Upgrading now, let me come back to you
if deleting the yarn lock fixes it please send me a diff between the old and new lock file.
Hey I have done the upgrade, and I don’t see any difference in the field there
And I am still seeing id in the field
try deleting your lock file and re installing and rebuilding the admin
rm -rf package-lock.json .cache dist ./node_modules/.cache
npm i
npm run dev
Tried this but still no luck
Okay mind opening a issue on GitHub - strapi/strapi: 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
@Boegie19 same issue
@Boegie19 did you find your solution?
If anyone finds a good solution to the problem, please let me know.
So far I have this quick fix, where I can change the Entry Point based on a short text field, but I’d love to have it based on the consultants name (not id).
God bless you, you are a genius.
Works like a charm, thank you, you are awesome… ![]()
I’m running strapi latest
│ Version │ 5.4.1 (node v20.8.0)
│ Edition │ Community
this issue is still present. Any idea how long will does it take to fix it?
Is it safer to downgrade to version 4 for production?
Thank you!
Alfredo
In my case, the issue was with the type of the “title” field. Long texts can’t be used as identifiers for an entry.
For Strapi 5.22.0 I saw the same issue.
Fix is the same as what someone earlier mentioned.
1 - Go to Content-Type Builder
2 - Go to the content type that has the relation field in question
3 - Go to “Configure the View”
4 - Hit the pencil icon on the relation field in question
5 - In the modal, change the value in the dropdown labeled “Entry title”



