Fix composite field creation

[thomtrp]

• composite field need to be formatted before being saved
• repository.create() does not do it. So we simply lose the composite fields on the way
• save() does it directly and doing create() before does not change anything

[Weiko]

LGTM

[greptile-apps]

PR Summary

This PR modifies the record creation workflow to fix composite field handling by simplifying the save operation.

• Changed create-record.workflow-action.ts to use direct repository.save() instead of repository.create() followed by save()
• Fixes issue where composite fields were being lost during record creation
• Removes intermediate validation step from repository.create()
• Ensures proper formatting of composite fields before database persistence
• Impacts workflow record creation functionality in twentyhq/twenty

_{1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Directly calling save() bypasses entity validation that create() provides. Consider wrapping in try/catch to handle validation errors gracefully.