Product Extension (PX#)
A Product Extension (PX) table stores values for product attributes that:
Do not fit into the Product table.
Depend on another dimension, such as time.
There are several PX table sizes—PX3, PX5, and others. Choose the smallest option that can hold your data to avoid wasting database storage.
Fields
name – Unique name of the Product Extension table. Every record keeps a back-reference (name of the table) to which is belongs.
sku – ID of the product for which this record keeps data.
createdDate – The date and time when the product extension was added to the table. Hidden by default.
createdBy – The user who added the product extension to the table. Hidden by default.
lastUpdateDate – The date and time when the product extension was updated for the last time.
lastUpdateBy – The user who updated the product extension for the last time. Hidden by default.
attribute1..# – Values of product attributes. Some of the 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.productExtension(String extensionName, Filter... filters) method or improve response time for other database queries. The change is related to the following tables:
PX3
PX6
PX8
PX10
PX20
PX30
PX50
Business Key
The PX# 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.