Working with data in Liquid

The built-in Liquid objects cover the standard StoreConnect data model. When your store holds data in custom fields or custom objects, you have to map that data before a template can read it.

:::note Mapping makes data readable, but for a custom object you defined yourself it does not make the data sync. Those objects also need a record-triggered Flow to push their records to your store. See Sync custom objects using flows. Custom fields on built-in objects sync automatically. :::

These articles cover both halves of that job: making the data available, then confirming it arrived.

In this section

• Add custom data fields to your store — map custom Salesforce fields and objects so Liquid templates can read them
• Verify custom data is available in Liquid — confirm mapped data is reaching your templates, and diagnose it when it is not
• Display dynamic content using Liquid queries — fetch Salesforce records inside a template with the query tag
• Write custom data back from a template — save changes to mapped custom fields with the update tag, and the four preconditions that make it fail silently