Customer Master Extensions

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

Click the Add button to add a new extension.
Enter a Name – You will use this name later in the calculation logic to identify, in which table you want to search data.
Set a Label – This is what users will see in the Master Data > Customer Extensions > Category drop-down menu.
Select the Size, which is the number of available attributes (3, 6, 8, 10, 20, 30 or 50).
In the Allow Search column, set whether this extension's attributes should be available in the advanced Customer filter (on the Customers page).
Allow Analytics Search – 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 determining which groups of people can see/edit this table.
Click OK and select the new extension from the list.
On the right-hand side panel, choose which column(s) is used as the Business Key. The system checks if the combination of business key 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, it will however be always part of the Business Key.
If Last Update Date column is selected as the Business Key, this column is not included in the file when the Product Extension is exported. This means that this file cannot be used for data update as it will fail on header validation.

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 right-hand side panel as a grid without data (even if the extension contains some).

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. The only exception when you can rename the Customer ID field is when the Customer Extension is decoupled from the Customer record.

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.