Business Problem:
Contact properties are currently structured in a flat, single-value format. While this works for simple data, it becomes restrictive when managing more complex or repeated information tied to a single contact.
Users need the ability to:
  • Store multiple related values under one field (e.g., multiple URLs, multiple IDs)
  • Structure grouped or repeated datasets (e.g., courses, enrollments, issue records)
  • Avoid creating dozens of flat fields to represent logically connected data
The current flat-field structure makes it difficult to scale contact data modeling for advanced use cases.
Desired Outcome:
  1. Multivalue Custom Fields: Implement the ability to add custom fields that support multiple values for contacts.
  • Use Case: For instance, a user could add a custom field that contains a list of URLs related to open issues in an external issue management system. This allows for comprehensive tracking and easy reference without switching between systems.
  • Flexible Data Types: Support various data types (e.g., string, number) as multivalue fields to accommodate different use cases.
  1. Nested / Structured Custom Fields
Support grouped or hierarchical data structures within contact properties.
Example:
Instead of: Course 1 Name, Course 1 Level, Course 1 Score
Allow: Courses → Course Name → Level → Score
Current Workaround:
Users currently have to create multiple single-value fields or manually compile related information outside the platform, which is time-consuming and less efficient.