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

Miva Developer Docs

A Data Builder field works out a finished feed row for every product, variant or category and stores it. It recomputes a record only when that record changes. A Feed Builder feed then writes out the stored rows instead of building them, which keeps feeds for large catalogs fast.

How it works#

  1. You add a field on the Data Builder tab under Settings > Utilities, and map fields the same way as in Feed Builder.
  2. The field’s All Products task stores a row for every active product (and every variant, if you turn that on).
  3. When a product, its stock, variants, images or category assignments change, the module queues that product. The field’s Queued task recomputes it.
  4. The stored row is a read-only custom field on the product, with the field’s code. A Feed Builder feed maps it with the Use Value as Feed transform and writes it as the whole row.

What a stored value looks like#

Each value is one complete row in the field’s Output Format:

Format Stored value
CSV One line, no line ending: TEE-RED-S,Feed Test T-Shirt Red S,20.00 USD
JSON One object: {"id":"TEE-RED-S","title":"Feed Test T-Shirt Red S","price":"20.00 USD"}
XML One record: <record><id>TEE-RED-S</id>...</record>

The value is a custom field like any other, so it also shows in the Product List grid when you add it as a column.

Compared with Feed Builder#

Feed Builder Data Builder
Builds rows Every time the feed runs Once per record, when it changes
Writes a file Yes No. The values are stored in the database.
Filters Products setting and conditions None. Every active product is stored; filter on the Feed Builder feed.
Source Can be changed Fixed when the field is created
Scheduled tasks One shared task One or two tasks per field
Header and footer Written to the feed Not used. Put them on the Feed Builder feed.

Pages in this section#