PIM Product Reader

If you are not familiar with what a Value Reader does or what it is used for, I recommend first checking out the article Value Readers.

Explanation:

The PIM Product Reader is one of the most common Value Reader being used, this is because its essential for every Product Export and also can be used to read their DAM references.

How to Configure:

“Limit product export to these classes” does exactly what it says: it limits the Value Reader to the selected classes. For example, if you apply the Electronics class, the Product Reader will only read values that are assigned to that class.

Configuration of the data Source:

“Always load the selected objects (header objects)” can be very useful when working with additional filter options. As the name suggests, this feature ensures that the selected objects are always read. For example, if you want to always include the Electronics header object, but other filters would normally exclude it, enabling this option will guarantee that it is still read.

“Filter objects by these Workflow Statuses” is a filter option that allows you to filter objects based on their workflow status. For example, you could configure the Value Reader to only read objects that are in Productive. However, keep in mind that most filtering is typically done in the job settings.

“Add Attributes of these Classes” is a feature that automatically adds the attributes of the selected classes to the mapping process. This can speed up the mapping, since you can preselect attributes through their classes.

“Add Attributes of these Classes (newline-separated)” is simply an extension of the Add Attributes of these Classes feature. Instead of selecting the classes, you can enter them manually, one per line.

Load referenced objects:

“Attributes that reference other objects” is a very useful feature. It allows you to specify attributes that reference other objects, such as a cross-selling attribute or an attribute related to the product, like spare parts. The items referenced in these attributes will be loaded into the export as well, for example, the spare parts.

“How many reference levels do you wish to export?” defines how many levels of referenced attributes will be included in the export. For example, if a spare part of your product also references another object, you can specify here how many levels deep the reader should go. The reference from your product itself counts as level 1, and any further references increase the level accordingly.