issue with Address field creation in self-hosted instance

[soft night]

Environment: Self-hosted Twenty CRM v0.53.8

Expected behavior: Self-hosted instance should allow "Address" field in the custom Property object. Cloud version works as expected.

Actual behavior: Self-hosted instance rejects field creation with "name not available" error

Steps to Reproduce: Try creating Address field in custom object when Company.Address exists

---

Details:
I am unable to create an Address type field with the name “Address” under Property object (custom object). It throws error: “The name “Address” is not available”.
However, in the cloud instance I'm able to have it (objects/properties/address)

When checking, I see that the only other occurrence of “Address” is in another object, Company (see the screenshot)

I created the “Addres” (with a single “s”) under Properties - no issues.
How can I resolve the issue and create a properly named Address field in the custom Property object?

[willow jetty]

Hello @soft night ! If it works on cloud very high chances this has been fixed in twenty latest version

[soft night]

thanks @willow jetty will check and revert

[young compass]

@willow jetty we have upgraded to latest version of twenty . I have attached the logs for further reference. Please assist

[willow jetty]

address is a reserved keyword

Please use a different name

For instance these are all reserved keywords:

const coreObjectNames = [
  'approvedAccessDomain',
  'approvedAccessDomains',
  'appToken',
  'appTokens',
  'billingCustomer',
  'billingCustomers',
  'billingEntitlement',
  'billingEntitlements',
  'billingMeter',
  'billingMeters',
  'billingProduct',
  'billingProducts',
  'billingSubscription',
  'billingSubscriptions',
  'billingSubscriptionItem',
  'billingSubscriptionItems',
  'featureFlag',
  'featureFlags',
  'keyValuePair',
  'keyValuePairs',
  'postgresCredential',
  'postgresCredentials',
  'twoFactorMethod',
  'twoFactorMethods',
  'user',
  'users',
  'userWorkspace',
  'userWorkspaces',
  'workspace',
  'workspaces',
  'role',
  'roles',
  'userWorkspaceRole',
  'userWorkspaceRoles',
];

const reservedKeywords = [
  ...coreObjectNames,
  'event',
  'events',
  'field',
  'fields',
  'link',
  'links',
  'currency',
  'currencies',
  'fullNames',
  'address',
  'addresses',
  'type',
  'types',
  'object',
  'objects',
  'index',
  'relation',
  'relations',
];

[young compass]

@willow jetty thanks for the inputs. I can see this commit on 11th march 2025. We are running version 0.54.6 in our self hosted instance. The twenty hosted version still allows us to create this field. May we know which version is hosted by twenty.

[willow jetty]

Unless I'm mistaken unable to do so even on cloud production

@young compass cloud production is always using the latest twenty version

[young compass]

@willow jetty thanks for the clarifications. I tried now and yes I could not create a Field name "Address" of the type Address in cloud. Just got confused coz we were able to do so sometime back. The attachment is from cloud twenty. Dont remember when exactly we created this. But thanks for the quick response. All sorted and resolved!!

[willow jetty]

No worries my pleasure !
You might have been creating it before we add validation on it 🤔
Interesting seems like there were no commands to migrate legacy fields name
I would recommend renaming your field on cloud prod just in case

[young compass]

@willow jetty Yes sure 👍