## Context Currently we have an unicity constraint in the DB but we don't return a clear error to the frontend before reaching the DB (which then throws a 500). This PR adds a validation check similar to what we have with field creation
## Context Currently we have an unicity constraint in the DB but we don't return a clear error to the frontend before reaching the DB (which then throws a 500). This PR adds a validation check similar to what we have with field creation