Created by potrace 1.16, written by Peter Selinger 2001-2019

Miva Developer Docs

The Source tab decides which records become rows.

Source#

Product or Category. Each row is built from one product (or variant), or from one category.

Changing the source clears the conditions and removes every mapped field except Code and Name, because the other fields don’t exist on the new source.

Products#

Product source only. This is the first filter: the feed reads only these products, then applies the conditions below.

Products Reads
Active Active products. This is the default.
All (including inactive) Every product
Available (in no availability group) Active products that are in no availability group, so every shopper can buy them
In Category Active products assigned to the listed categories
In Price Group Active products assigned to the listed price groups
In Availability Group Active products assigned to the listed availability groups
Not In Category Active products not assigned to the listed categories
Not In Price Group Active products not assigned to the listed price groups
Not In Availability Group Active products not assigned to the listed availability groups

The category and group choices show a text box for comma-separated category codes or group names, and a Lookup button to pick them. Saving checks that each code or name exists. Errors read like “Category cannot be blank” or “Price Group ‘Spring Sale’ does not exist”.

Most channels reject products shoppers can’t buy, so the ready-made channel files use Available.

Include product variants as separate feed rows#

Product source only. Each variant becomes its own row with its own code, SKU, price, stock and attribute values, and the product code in item_group_id. See Variants.

Include#

All products includes every record the Products setting reads. All products with conditions includes only records that match the conditions. For a Category source the wording is “categories”.

Conditions#

Each condition has a field, an operator and a value. Choose whether a record must match all or any of them.

Operator Matches when the field
is empty is blank
is not empty has any value
equals equals the value, ignoring case
not equals doesn’t equal the value, ignoring case
contains contains the value, ignoring case
greater than is greater than the value
less than is less than the value

The value box is hidden for is empty and is not empty.

Conditions are checked against the product, before variants are expanded. A condition on Price checks the product’s price, not each variant’s.

Example: the ready-made files include products with a price above zero:

Field Operator Value
Price greater than 0

Products setting or a condition?

Use the Products setting for categories and groups. It filters in the database query, so the feed never loads the other products. Conditions are checked one product at a time after loading.