Attributes

Attribute selection

The following attributes can be used to configure the dialog box for selecting attributes:

  • ipim.web.select.attributes.dialog.select.limit: This property can be used to limit the number of attributes that can be selected. As soon as the limit is reached, the Add all button turns inactive and no further attributes can be selected. The same applies if the number of selectable attributes exceeds the limit.
Example: The limit is set to 25.
  • ipim.web.masterdata.attributes.meta-attributes.include: Using this property you can specify whether attributes of the “Meta attribute” type, attributes of the “Meta attribute definition” scope or both kinds of attributes can be selected:
    • meta-definitions (default): Only attributes of the “Meta attribute definition” scope can be selected.
    • meta-attributes: Only attributes of the “Meta attribute” type can be selected.
    • meta-attributes, meta-definitions: Both kinds of attributes can be selected.
INFO
Attributes of the “Meta attribute” type are the superordinate level in which multiple attributes of the “Meta attribute definition” scope can be combined.

Category product relation attributes

First introduced in version  5.5.0: Via the property ipim.core.attribute.string.htmleditor.largetexts it can be specified if it is possible to maintain multiple values for string type “Category-product-relation” attributes. For this purpose, the respective attributes are allocated to the property as its values. 

Deleting attribute values via file import

Using the property supplier.import.delete.keyword you can define a keyword, that allows you can delete the values of attributes, texts or prices by uploading a file that contains this particular keyword for the respective attributes, texts or prices in the “Product data update” app.

Note
The option to delete prices was first introduced with version 5.4.2.
  1. Use the “Export” action of the action menu to export the respective product data as an .xlsx file.
  1. In the .xlsx file, replace the attribute values that you want to delete by the keyword which was specified by the property supplier.import.delete.keyword.
In the example, the value “deleteThisPrice8945” was defined for the property. This deletes the value of the “Bulletpoint 2” attribute for the product “100184” once the data shown here has been imported.
  1. Go to the “Product data update” app and import the .xslx file with the product data as described here. Once the import is done, the corresponding attribute values in the iPIM system are deleted.

Display of inherited attribute values

Inheritance along product structure levels

Via the property ipim.core.attribute.showproductvalues it can be specified whether in tables attribute values which were inherited from the product level are shown subordinate product structure levels. That means, attribute values maintained on the product level are also shown on the variant or item level, whereby this is indicated by a corresponding indicator. The property can possess the following values:

  • true: Attribute values maintained on the product level are also shown on subordinate levels.
  • false: Attribute values maintained on the product level are not shown on subordinate levels.
Note
Since version 5.6.1, the property also effects that attribute values maintained on the variant level are also shown on the item level.

Inheritance along context levels

Via the property ipim.core.general.maintenancelevel.showtemplatevalues it can be specified whether attribute values which were inherited from superordinate context levels are shown in tables. The property can possess the following values:

  • true: Attribute values maintained on superordinate context levels are also shown on subordinate levels.
  • false: Attribute values maintained on superordinate context levels are not shown on subordinate levels.

Display of invalid lookup values

First introduced in version 5.5.3: Via the property ipim.web.apps.toolbox.attributes.hide.invalid.lookup.values it can be specified whether the menu for selecting lookup values shows invalid lookup values or not. The property can possess the following values:

  • false (default): The menu shows valid as well as invalid values whereby they are shown in groups.
  • true: The menu only shows valid values.

This screenshot shows the menu with the property set to “false”
INFO
For example, lookup attribute values can be invalid if there is a dependent value mapping between two attributes. If a particular value is set for the source attribute, for the dependent attribute, all lookup values that are not mapped to from the source value are deemed invalid. For example: If there is a dependent attribute mapping from the value “Darkorange” of the attribute “Orange” to the value “Darkgreen” of the attribute “Green” and the value “Darkorange” is set for the attribute “Orange”, “Darkgreen” is the only value that can be selected for the attribute “Green”, given the prerequisite that no other dependent attribute mappings exist for the value “Darkorange”.

Length of strings

Using the property general.freetext.maxlength you can specify the maximum number of characters for localized and non-localized string attributes. For this purpose, the desired number is assigned to the property as its value.

List of values attributes

First introduced in version 5.4.2: Via the property ipim.web.attributes.filter.inactive.values you can specify whether inactive values are shown in menus for selecting values of a list of values attribute. The property can possess the following values:

  • false: Inactive values are shown.
  • true: Inactive values aren’t shown.

Localizing attribute values etc.

The iPIM system supports two different strategies two different strategies regarding the localization of attribute values, whereby this is controled via the property “ipim.web.attribute.formatting-strategy”. This property can possess the following values:

  • legacy: Lookup values and units are localized in the user interface language. Numerical attributes and date attributes are formatted according to the formatting rules of the user interface language. The selected data language (locale) only affects localized strings and texts. Only attribute values that are maintained in the selected data language are displayed. If no value is maintained, the corresponding field remains empty.
  • data-locale: Only the names respectively descriptions of types and attributes are shown in the user interface language. Everything else is shown in the data language (locale). This also means that numerical attributes as well as date attributes are formatted according to the formatting rules of the of the data language (e.g. the German formatting with a comma as decimal separator and dots for grouping or the English formatting with a dot as decimal separator and commas for grouping).
Type of value legacy data-locale
Attribute name/description User interface language (UI) User interface language (UI)
Type name/description User interface language (UI) User interface language (UI)
Lookup values (list of values attributes) User interface language (UI) Data language (locale)
Localized strings Data language (locale) Data language (locale)
Formatting of numerical values User interface language (UI) Data language (locale)
Formatting of date values User interface language (UI) Data language (locale)
Units of measurement (UOMs) User interface language (UI) Data language (locale)
Note
  • The “legacy” setting corresponds to the localization strategy used in the “Swing Client”.
  • Using the property “ipim.web.attribute.formatting-strategy.edit” you can specify that attributes are edited in the language in which they are shown. For example, if the property is set to “data-locale”, in the respective selection menu lookup values are shown in the data language. The same applies to the way the calendar menu is displayed.
INFO
The user interface language is the language in which the user interface is localized. The data language is the language in which the data (i.e. attributes and attribute values) are localized.