When is it advisable to create a data type?

Creating a data type is advisable when there is a need for a logical collection of custom fields across multiple schemas. This approach allows for standardized definitions and consistent usage of these fields, ensuring that data is organized and accessible across various contexts within the Adobe Experience Platform.

By using a data type, you can define a group of related fields that can be reused in different schemas. This promotes efficiency and helps maintain data integrity, as any changes to the data type will automatically reflect in all schemas that utilize it. Additionally, it facilitates better data governance by providing a clear structure that can be used across diverse data practices and applications.

In scenarios involving complex data models or transitioning to production, while thoughtful structuring is important, the creation of a data type specifically addresses the need for coherence in data representation and reuse across multiple areas. This ensures a more scalable and manageable approach to data architecture within the platform.