Custom Address Fields Requirements and Limitations

Custom Address Fields Requirement: State and Country/Territory Picklists

Custom Address Fields uses picklists for the State and Country address fields. For more information, see Configure State and Country/Territory Picklists.

Custom Address Fields Requirement: Package Deployment

If a package contains a custom field with the Address field type, package deployment requires that Custom Address Fields is enabled in the target org.

Custom Address Fields and Org Limits

For custom compound fields, each component counts as one custom field toward your org’s allocations. Thus each custom address field counts as nine custom fields: one each for street, city, postal code, country code, state code, geocode accuracy level, longitude, and latitude, plus one for internal use. For more information on the allocations for your org, see Salesforce Features and Edition Allocations in Salesforce Help.

Limitations for Custom Address Fields

Before you enable Custom Address Fields or add a custom address field, understand the limitations of this feature.

These items aren’t supported with custom address fields.

• The conversion of address data into custom fields of type Address from custom fields of other types.
• Approvals
• Data Import Wizard
• Fuzzy matching
• Composite API
• Field Encryption
• Field Sets
• Flow Screen Input Component: Address
• Lead Conversion
• Lightning Web Components
• Merge Fields
• Search, including global search, lookup search, SOSL queries, and Search Manager
• Visualforce pages
• Workflow

Salesforce hasn’t validated custom address fields with these items.

• Schema Builder
• Web-to-Case and Email-to-Case
• Generating Leads from Your Website
• Filtering in a related list
• Bulk API 1.0
• Data Loader

This functionality is either unavailable or limited with Custom Address Fields.

• As with standard address fields, you can’t mark a custom address field as required.
• You can’t use the DISTANCE function with a custom address field.
• To export data stored in custom fields of type Address, use API or SOQL queries. Bulk API doesn’t support the export of custom compound fields.
• The error message when you attempt to export a custom address field with Bulk API incorrectly states that the functionality isn’t enabled. Bulk API doesn’t support the export of custom compound fields.
• To populate a custom address field with imported data, use REST API or Bulk API 2.0.
• Search queries only support the data stored within the Street component of custom fields of type Address. The State, City, Postal Code, and Country components aren’t supported for search.
• In Skinny Tables, you can’t select a component of a custom address field as partition column.
• When configuring search results for an object, custom address fields aren’t supported in Search Filter Fields (only available in Salesforce Classic). If you specify a custom address field as a Search Filter Field in a search layout, package installation and Metadata deploy() fails.
• Compound address fields aren’t supported in reports. To include a custom address field in a report, add the individual address components, such as street, city, state, and zip.
• When using a custom address field in a Data Integration Rule, the Country and State components are unavailable for field mapping.
• You can’t rename the labels for the individual components of a custom address field.
• You can localize the label of a custom address field. However, you can’t localize the labels of the individual components within a custom address field.
• The word “Address” isn’t appended to the section label for a custom address field. If you include the word “Address” in the field label, it’s included in the label for every component. For example, “Warehouse Address (State)” instead of “Warehouse (State)”. These labels are inconsistent with the label behavior for standard address fields.
• The length of the GeoCodeAccuracy field for custom fields of data type Address isn’t consistent with standard field of type Address.