Customer Master Extension

In this section, you can set up new Customer Extensions and their structure.

Click the Add icon to add a new extension.
Enter a Name and select a Size, which is the number of available attributes (3, 6, 8, 10, 20, 30 or 50).
Optionally:
- Set up a Label and Searchability.
- Set Analytics Searchability – If enabled, you can make this extension's attributes available in the Customer input filter when the datamartCustomerGroupEntry() method is called. The returned customer group object can be used in a Datamart query as soon as you create corresponding Data Sources and propagate the Customer Extension's attributes as fields into a Datamart – use the Template that is created automatically when you create a Customer Extension. This feature is intended above all for Agreements & Promotions and Rebates.
- Set view/edit permissions – Which groups of people can see/edit this table.
  There is a limit of 255 characters for user group strings combined together. If you need to select more user groups and/or they have very long names, use the Advanced Configuration Option 'allowedLengthOfGroupsSelectionForOX' which specifies the maximum allowed group string length. It works only for CX stored in the JSON.
- Choose which column(s) is used as the Business Key. The system checks if the combination of business keys values is unique and avoids duplicates. If duplicated rows are loaded, the system will update the existing records with whatever comes last.
  Customer ID can also be selected as the Business Key.

If you later want to change the number of attributes available for the given customer extension, use the Change number of attributes icon.

When changing the number of attributes for an extension with large amount of data, make sure that no calculations will use that customer extension during the data migration. Consider stopping the adapters and calculation flows and do not allow the end users to trigger any calculation. In extreme cases, consider temporarily dropping the unnecessary database indexes for the source and target CX table and recreate them after the migration.

When an extension is selected, the structure is visible in the lower pane as a grid without data (even if the extension contains some). This grid is just to set up the columns.

If you need to rename the 'Customer Id' field, you need to do that in the Customer master. This way the change is propagated to all Customer Extensions and data consistency is maintained.

After changing Customer Master Extensions, you need to log off and log in again to see the changes reflected in other parts of the application. Changing the name or type of an existing Customer Master Extension that is used in a calculation logic will require a change there too. Note that the configuration is cached and it can take up to five minutes for a change to take effect.