Editing and Managing Schema Fields

• Interactive Editing: The Schema Editor provides a user-friendly interface to directly modify your schema within the Customer Data Cloud Console.
• Scalability: The system supports adding up to 1000 custom fields beyond the default schemas, along with 1000 Subscription objects and 1000 Consent objects per site, ensuring scalability for growing data needs.
• Dynamic Updates: New fields added to the schema become immediately available for use, allowing for real-time adaptation to changing business requirements.
• Internal Fields: These fields are designed for server-side access only, accessible through API calls like accounts.getAccountInfo and account.search, providing a secure way to store sensitive data.
• Nested Fields: The Schema Editor supports the creation of nested field structures using periods to separate levels (e.g., data.my.field1 and data.my.field2), enabling complex data relationships.
• Security: Write Access and Required field properties are not editable for internal fields, enhancing data security and preventing unauthorized modifications.
• Permissions-Based Access: Access to the Schema Editor is controlled by permissions, ensuring that only Console users with appropriate authorization for APIs like accounts.getSchema and accounts.setSchema can access and modify the schema.

• Schema Visibility: Gain a clear view and understanding of your existing schemas, facilitating informed decision-making.
• Self-Service Updates: Empower yourself to quickly update schemas without requiring developer intervention, reducing bottlenecks and improving agility.
• Enhanced Security: Benefit from restricted access, ensuring that only authorized personnel can modify the schema, safeguarding sensitive data.

To access the Schema Editor, ensure that your account has the necessary permissions. You can find the Schema page in the Console's left-hand menu under the Advanced section.

In this video, we’re going to walk through how to customize the Account Schema in SAP Customer Data Cloud. Using the Schema Editor, you will learn the step-by-step process for adding new fields and configuring the properties of standard fields to match your business requirements.

The WriteAccess property determines whether unsigned requests can write to a specific field. This is crucial for controlling data security and integrity. 

The supported values are:

• serverOnly (default) - Only signed requests coming from the server are allowed.
• clientCreate - Unsigned requests coming from the client are allowed to write into this field if it was not previously set.
• clientModify - Unsigned requests coming from the client are allowed to write into this field and modify existing values.

Addresses fields are generally available in the Schema Editor, allowing you to capture and manage customer address information.

However, there are some important considerations:

• Periods (".") are not allowed in an addresses field name, and you cannot create hierarchical nested fields to set up complex addresses objects.
• SAP Customer Data Cloud saves your created delivery field as a nested object within an Addresses Object REST, referenced as addresses.delivery. The address object and its nested object have a predefined structure and specific properties.​
• You can set any top-level field of your address to required. Note that only specific top-level fields can be verified by SAP Data Quality Management, microservices for location data, eg., countryISOCode3, city, houseNumber and zipCode, etc.
• Users are allowed to edit address data, for example, on their profile. These changes are reflected here in the top-level address data, which makes them no longer verified by SAP Data Quality Management, microservices for location data.

For more information on how to add the addresses fields to the UI screens and validate the addresses fields with the DQM service, please refer to ​Data Quality Management (DQM) | SAP Help Portal

Custom Login Identifiers are used by your internal systems, for example, Frequent Flyer ID, loyalty ID number, or any internal reference number. They provide a powerful way to link customer data across different systems.

• Set up custom identifiers used by internal systems or services as an internal customer reference
• Use custom identifiers to retrieve customer accounts in the relevant internal systems
• Simplifies your back-end integrations with internal systems or services that retain an internal customer reference
• Custom identifiers must be defined at the parent level (up to 3 custom identifiers per site group). Child-site override is not permitted.

For more information, refer to the Custom Login Identifiers documentation in the SAP Help Portal.

• Plan your schema carefully: Before making changes, consider the long-term impact on your data model and applications.
• Use descriptive field names: Choose names that clearly indicate the purpose and content of each field.
• Document your schema: Maintain documentation that describes the purpose and structure of your schema.
• Test your changes: Thoroughly test any schema changes in a non-production environment before deploying them to production.
• Monitor your schema: Regularly monitor your schema for performance and data quality issues.