Product Extensions

Product Extensions (PX) are attributes of products that do not have a strict one-to-one relationship with a product: the attribute can change over time or a product can have multiple attributes of the same type. Product extensions accommodate these attributes. Product extensions can be used in price calculations. Product extensions can be classified by category.

Product extension structures are set up by an administrator in Configuration. The first column contains the Product-Id. The other columns can contain any type of value. As for the number of columns, you can choose a product extensions table with 3, 6, 8, 10, 20, 30 or 50 attributes.

 For each column, there is a limit of 255 characters. For product extension with 50 attributes, the limit is 70 characters for each column. If you change the size of the product extension from a lower number of attributes to 50 attributes and some of the attributes have more than 70 characters, a warning is displayed and the character string is truncated.

To access Product Extensions:

  1. Go to Master Data > Product Extensions.

  2. Select the required Product Extension from the Category drop-down.

The available options are:

  • Add a product extension. You have to enter the ProductID, all other data are optional.

  • Import product extensions. Export the current table into the CSV or XLSX format (XLS is not supported), make your changes and import the file back. The existing data can be replaced or appended.

  • Duplicate the selected item.

  • Edit the values by double-clicking the field that needs to be changed.

  • Mass edit all, filtered or selected fields. Also enables you to add or remove attributes. A new pop-up window will open. Select the Attribute, Change (operator) and enter a new Value. Click the Edit button to confirm the changes.

  • Delete an item. The item will be deleted immediately.

When deleting a PX table, you can decide whether the underlying data will be also deleted from the DB. There is a system-level "stale OX" command:

/pricefx/system/system$staleox/<partition> – Does not delete data, only detects. The partition URL parameter is optional; if omitted all partitions are checked.

/pricefx/system/system$staleox/<partition>/delete – Data will be deleted. The partition URL param is mandatory.

  • Mass delete all, filtered or selected items.

  • Export the data into MS Excel.

  • Filter the items by product extension or product master attributes.
    See also a filtering limitation when filtering Products using Product Extension attributes in an advanced filter.

Note: Automatic loading of data into the Product Extension tables can be disabled by the Load content of PX/CX/SX automatically option in General Settings.

Use Product Extensions in Filters

Fields from product extensions can be used in advanced filters in product pickers throughout the application and in Price List / Live Price Grid detail page for item filtering.

Follow these steps:

  1. Go to Administration > Configuration > Master Data > Product Master Extensions.

  2. Make sure that the Allow Search option is enabled for the extensions whose fields you want to use in filtering.

  3. Open a product picker, for example in Agreements/Promotions.

  4. In the Input Parameters section, click Browse next to the Product(s) input field.

  5. In the Select Product Group dialog, click Filters.

  6. Click on <add filter> and select a field you want to filter on, for example IncoTerms: INCO1.
    Note: Any field from the customer extension tables will be present in the list with the format CX name: field name, for example Salesman: SALESMAN.

  7. Keep on adding fields to filter on by clicking on <add filter>.

  8. Save the filter to a new preference. Give the preference a name and select if it is visible to everyone or your default preference.
    You will then see the filter set on the product picker screen.

 When you filter in Products using Product Extensions attributes or in Customers using Customer Extensions attributes, using subclauses will return correct results only if the optimizeQueriesToExtensionTables option is set to true in pricefx-config.xml (it is by default).

Found an issue in documentation? Write to us.

 
Pricefx version 12.0