Compound fields are intended for creating more complex data structures by combining multiple simple fields into a single field. These fields help organize related information and ensure consistent data entry.
The following are the examples of compound fields:
- Address field: Groups related address components
- Street address (text)
- City (text)
- State/Province (selection list)
- Postal code (text or number)
- Country (selection list)
- Name field: Combines name components
- First name (text)
- Last name (text)
- Title/Prefix (text)
- Suffix (text)
- Social media profiles: Collection of profile links
- Platform type (selection list)
- Username (text)
- Profile URL (link)
- Product specifications: Group of product details
- Dimensions (multiple number fields)
- Weight (number field)
- Materials (text or selection list)
- Features (multiple text fields)
The following are the benefits of compound fields:
- Data consistency: Ensures all related pieces of information are collected together.
- Simplified data entry: Presents related fields in a logical grouping.
- Improved validation: Provides the ability to validate the relationship between component fields.
- Better organization: Keeps the field list cleaner by grouping related fields. This can be helpful when fetching data through JSON:API, as it simplifies the data structure that must be fetched and parsed.
- Enhanced reusability: Provides the option to reuse the entire compound field across multiple content types.
Compound fields are particularly useful when you need to collect the same set of related information across different content types or when the relationship between pieces of information is important to maintain.
Compound fields
Compound fields are intended for creating more complex data structures by combining multiple simple fields into a single field. These fields help organize related information and ensure consistent data entry.
The following are the examples of compound fields:
- Address field: Groups related address components
- Street address (text)
- City (text)
- State/Province (selection list)
- Postal code (text or number)
- Country (selection list)
- Name field: Combines name components
- First name (text)
- Last name (text)
- Title/Prefix (text)
- Suffix (text)
- Social media profiles: Collection of profile links
- Platform type (selection list)
- Username (text)
- Profile URL (link)
- Product specifications: Group of product details
- Dimensions (multiple number fields)
- Weight (number field)
- Materials (text or selection list)
- Features (multiple text fields)
The following are the benefits of compound fields:
- Data consistency: Ensures all related pieces of information are collected together.
- Simplified data entry: Presents related fields in a logical grouping.
- Improved validation: Provides the ability to validate the relationship between component fields.
- Better organization: Keeps the field list cleaner by grouping related fields. This can be helpful when fetching data through JSON:API, as it simplifies the data structure that must be fetched and parsed.
- Enhanced reusability: Provides the option to reuse the entire compound field across multiple content types.
Compound fields are particularly useful when you need to collect the same set of related information across different content types or when the relationship between pieces of information is important to maintain.
Acquia Source