Adding UID with attached field to existing Collection Type returns null

[malgamves]

Bug report

Describe the bug

Whenever I add a UID with an attached field to an existing Collection Type and query that Collection Type, the UID returns null even though the field is automatically filled in due to the field it's attached to being filled in. This is because we don't trigger a save in the entry as we technically haven't made a change because it was automatic.. when i add a UID with no attached field and go to the entry view to add content to the UID with no attached field, the save button is visible and i can click it after which both UID show in response.

Steps to reproduce the behavior

1. Create a Collection Type with a short text field
2. Add some entries to the collection type you just created
3. Go to the Content type builder and add a UID which is attached the short text field you made earlier
4. Query endpoint corresponding to collection type
5. See error

Expected behavior

The Save button should be clickable in entry view because of the UID with an attached field that was automatically populated or by default the save should be triggered when the UID is populated so null isn't returned

System

• Node.js version: 14.16.0
• NPM version: 7.24.1
• Strapi version: 4.0.0-beta.13
• Database: sqlite
• Operating system: Windows 10

Additional context

Add any other context about the problem here.

[petersg83]

Indeed the save button is disabled.
We would maybe need a way to tell the user that the field is empty and that we suggest them this UID "xxx" (based on another field). It would need to be reviewed by the design team.

Also, should we migrate all existing data by filling the new UID field?

[malgamves]

Hey @petersg83 usually users want the UI to be related to a single field so changing the field would not be great, however I'm for suggesting visually that the UID is already taken and asking them to edit it/add a new one.

Also we could migrate the existing data yes. Would it be best practice?

[petersg83]

I'm not sure to understand the first part. However, there is already a US created to fix it. Here is the design :

Regarding the migration, I'm not sure if it's a good practice. If there is no issue for that for the moment I think it's better to let it as it is, which means without migration