bronze flax
I'm reporting a critical UX/Logic blocker persisting since v1.17 regarding the People system object and the phone field (set to Unique).
The Issue:
Accidental Creation: If a user clicks "Create Person" by mistake or exits an incomplete record, Twenty saves it with a null/empty phone.
Immediate Soft-Lock: The moment you try to create a new person, the system blocks it immediately with a "Value already exists" error. It treats the new empty state as a duplicate of the previous accidental record.
Result: You cannot create any new People until you manually find and delete the "ghost" record.
Question:
Since "Required" fields are still not supported for system objects, what is the best practice to prevent this? If Workflows are the answer, how can we block the UI from saving if phone is empty?
This is severely affecting my MCP-remote integrations on Windows. Any update on a "Non-nullable" toggle?
mighty sail
