Introduction

Introduction

Product Fields Library is a revolutionary way to enrich data about every product. Originally, the application required knowledge of which data based on the Master Model you wanted to add, as well as configuring it manually using rules.

This is no longer required. The Data Octopus team has prepared predefined additional product data and the rules that build it. The effort and knowledge required have been reduced to a minimum, and users are effectively inspired by what they can and should add and how to use it in business.

Users no longer need to come up with the idea of adding a value that segments products by revenue, first- or second-level profit, or price. They only need to decide that it is valuable to them and select the field, and the application will generate it automatically.

We have also implemented a solution that prevents incorrectly defined mappings from being run, helping protect product selection and the quality of the output feed.

You will find more information below. We believe Product Fields Library will significantly speed up work with data and lower the required threshold of knowledge and experience.

To access it, first select a model in the Model and data mappings section, then open the model fields and mapping tab and click Add field from library.

Opening a selected product field displays its detailed description, suggested uses, and information about the import fields required to use it. These appear at the end of the description in the Input data section (Delivery time type is an example).

Validation

After adding most Product Fields, you can immediately preview how they work, even before running the mapping, using the preview option.

Product Fields that use the Segmentation and Rank functions cannot be previewed, because these functions are only executed after running the mapping (Run mapping).

If a newly added Product Field in the Master Model is highlighted in orange and shows Error, the import is missing the field or data required to use it. This also automatically prevents the mapping from being run.

Opening the mapping editor for the Product Field showing Error displays information about exactly which field is missing.

To run the mapping again, you can:

• open the mapping editor for the Product Field and replace the missing fields with fields available in the import
• add the missing data, for example through a lookup table
• remove the Product Field with missing data

To use a Product Field in your strategy, create a view with the new field and then a strategy based on it, or assign it to an available custom label in the feed.

The Product Fields Library in the application was built using conditions and rules, which are covered in a separate article.