Any given field in PIM is an attribute, with a given datatype belonging to a certain set.

Option to create attributes not covered by default fields.

Health check

The heart icon on attribute details will display if the field is in use or not, and if there are data holes to cover.

It offers to delete content before deleting the attribute itself.

If data or attribute is deleted by mistake, it cannot be reversed.

Below is a list of attributes not default in PIM, but where functionality is triggered in the webshop based on the attribute code and datatype.

To work correctly please create attributes with codes and datatypes as shown. Label and Set can vary without affecting the functionality.

Code: addon-products datatype: product-relation

On the product detail page in PIM, enter relevant product ID's that the customer should be prompted to buy along with the main product.

When the customer goes to the product detail page in the webshop, the two product ID's will be presented as addons to buy.

Code: stock-value data-type: decimal

An attribute field with the code stock-value and data-type: decimal, is the default field used by the webshop to determind the qty in stock.

Code: remote-image data-type: Resource URL (single)

This attribute gives the option to use an external URL as product image. It is important to stress, that this solution should only be temporary. If the image is changed/removed from the external site, then it will no longer work. Note also that large images entered in this matter will make large category lists slow. This option should be used only on demo- or test-sites. It will also require that the external site is whitelisted in the security section of the Chainbox toolbox in CMS Umbraco.

Attributes are any fields existing in PIM. These can be anything from Product-fields being mapped against the ERP-system, product specifications such as colors or measurements to lists with multiple choices etc.

Due to the potential number of attributes, it is recommended to have a clear strategy of sets to organize the attributes under, and a systematic approach to creation of new fields.

Label

Name of attribute as shown in PIM views.

Code

Code will be defined automatically from the label, or can be entered/overwritten manually. (Once the attribute is created, the code cannot be changed, since it is the unique identifier of the attribute)

Sortorder

Option to enter a sortorder, that will be active when working with attributes in view-filters and define attributes.

Datatype

Choose the datatype carefully depending of the type and use of the attribute. Once the attribute is create, the datatype cannot be changed. There can be attributes with pre-assigned functionalities that acquires a certain datatype. Please check "Attributes with Umbraco functionality" for info on this.

Set

Choose what set to sort the attribute under. When working with many attributes, a clear set-structure is of great advantage. Option to create additional sets under "Define" - "Sets". The Sets ERP Mappings auto or custom should ideally only contain attributes with ERP-mapping. Meaning the data of the attribute is owned and controlled by the ERP-system, made visible by the Padlock icon appear next to the data in the field.

Read only

New option to mark non-ERP-mapping fields as Read only. This will ensure, that the originally entered data is protected from updates through imports or in product view. Same as with ERP-mapped fields, a padlock icon will appear next to the data to make visibel the that content is read only.

ERP mapping/Map to ERP field

If the initial setup of the installation includes integration with the ERP-system, then the initial mapping of ERP-fields will be in place. It is still possible to add additional mappings to ERP-fields not prior mapped. In case new fields are create in the ERP-system to be mapped in PIM, please contact your Chainbox developer to ensure, that the new fields are part of the export from the ERP-system.

Before deleting an attribute, make sure to investigate how it is used, and what content exists that should be erased before the attribute itself is deleted.

Determine content of an attribute

Used in categories

Easiest way to determine if content exists, is to navigate to categories, click the category hierarchy and export to CSV.

Search or browse to the relevant attribute and tick it to include in export. Click "Start export".

Navigate to Import Export - Category CSV exports, and download csv file.

Should multiple category hierarchies exist please repeat.

Navigate to categories and manually erase content of attribute in question.

Used in products

Export to CSV

On the product view, click the export csv icon. Select the attribute in question with other attributes you wish to see. Click "Start export"

Navigate to Import Export, Product CSV exports and download file.

Filter on product view

If the attribute is not widely used, it could be sufficient to create a filter and scroll through the content.

Erasing content of an attribute

Below are two examples how to easily delete content in an attribute.

Health check

Navigate to Define, Attributes and search out and click the relevant attribute. Click the health check icon. Click the Delete button

Click "OK" to confirm action. Option to repeat the click on health check to confirm that all products now are missing data.

Bulk actions

On the product view, click bulk action icon and choose "Manage attributes". Search and select the relevant attribute. Click "Delete". Click "Apply".

This will delete data in attribute field on any existing product.

Click "Confirm" if statement is correct.

Deleting an attribute

With all content removed, the attribute itself can be deleted.

Navigate to Define, Attributes. Search and click relevant attribute. Click "Delete attribute".

Check attribute name and if correct, confirm deletion by clicking "Yes, delete"