Customer Extension (CX#)

The CX table holds values of customer attributes which:

  • either did not fit into the Customer table

  • or whose values also depend on some other dimension, like time.

There are several sizes of CX tables – CX3, CX6, CX8, etc. Use the smallest one which will be able to hold your values, so that you do not waste space in the database.

Fields

name – Unique name of the Customer Extension table. Every record keeps a back-reference (name of the table) to which is belongs.

customerId – ID of the customer for which this record keeps data.

attribute1..# – Values of customer attributes. Some attributes can be used as a part of the business key, e.g. validity of this record or for which sales organization this record is valid, etc.

attributeExtension – Attribute extension columns can be added on the top of the table’s regular attribute columns. Stored in the database in JSON format, they allow you to exceed the character limit that applies to regular columns. Available since version 14.0.

In the Rampur 13.0 release, we have added an index to the following attribute fields: attribute1, attribute2, attribute3. This enhancement should improve response time when attribute1, attribute2, or attribute3 are used in filters with the search methods api.find([...], Filter... filters), with the api.customerExtension(String extensionName, Filter... filters) method or improve response time for other database queries. The change is related to the following tables:

  • CX3

  • CX8

  • CX6

  • CX10

  • CX20

  • CX30

  • CX50

Business Key

The CX# table does not have a database unique constraints because you can use also some attributeX fields as a part of the unique key.

So you can define a business key which tells the system which fields form a unique key from business perspective.

Found an issue in documentation? Write to us.

Â