Keeping your content up to date

Your catalogue changes. Prices move, products arrive, descriptions get rewritten. Keeping Rubikc current means running the same two stages again — by hand, or on a schedule.

Your edits are kept

Read this before you avoid re-running anything

When a transform runs again, generated blocks that you have edited since are left alone. Your changes are not overwritten.

This is on by default, and it is what makes re-running safe. Without it nobody would ever run a transform twice, and their storefront would drift further from their catalogue every week.

Two things to keep in mind:

• It protects blocks you edited. Generated blocks you have not touched will be rebuilt, which is usually what you want — that is how a changed description reaches your storefront.
• Blocks you created yourself, rather than ones a transform generated, are not the transform’s to change.

Running things again

Sync whenever you want current data. It is always safe.

Transform when you want that data reflected in your cubes. Transforming is also how you apply different choices to content you have already built.

Automations

An automation runs a sync or transform on a schedule so you do not have to remember.

A daily sync suits a catalogue that changes often; weekly is plenty for most.

Before scheduling a transform

A scheduled transform runs unattended. Run it by hand first and check you are happy with what it produces — your own edits are protected, but everything else it builds will change.

When a scheduled run fails

Nothing interrupts you when a scheduled run goes wrong, so it is worth checking occasionally.

• Sync logs for problems pulling data in.
• Transform logs for problems building from it.

Next

Sources and InboxWhere imported material lives before it becomes a cube.