Is it possible to use choices from a MetaObject definition in a section schema?

Technical Q&A

Topic summary

Main issue: Whether a Shopify section schema can reference and reuse the preset choices from a Metaobject’s field (e.g., a testimonials metaobject with a “type” field offering choices like “Product Review” and “Customer Experience”) so the section setting doesn’t duplicate those options. Example intent: a testimonials.liquid section setting using a type like “shop.metaobjects.testimonials.type” to auto-populate choices.

Response: The only reply is generic and not Shopify-specific. It discusses possibilities in various frameworks (React/Angular/Vue, ORMs, OpenAPI/GraphQL) without addressing Shopify Liquid, section schema, or metaobject definitions.

Status and outcomes:

  • No concrete method, code, or confirmation for Shopify was provided.
  • No decisions or actionable steps emerged.
  • The question remains unresolved in the Shopify context.

Context: In Shopify, Metaobjects are custom content types with fields that can have predefined choices; the OP seeks to surface those choices directly in a theme section’s settings.

Summarized with AI on January 11. AI used: gpt-5.
1

Let’s say I have a testimonial MetaObject with a field “type” that’s limited to preset choices like

  • Product Review
  • Customer Experience

Now I would like to create a testimonials.liquid section with a setting where I can pick the testimonial type. Ideally I don’t need to duplicate the choices.

So my question is, is there any way of accessing the choices from the metaobject, something like this:

{% schema %}
{
  "name": "Testimonials",
  "class": "section",
  "tag": "section",
  "disabled_on": {
    "groups": ["header", "footer"]
  },
  "settings": [
    {
      "type": "shop.metaobjects.testimonials.type",  // <<<< THIS
      "id": "type",
      "default": "Product Review",
      "label": "Type",
    },
2

In general, the ability to use choices from a MetaObject Definition in a Section Schema would depend on the capabilities and features of the technology or framework you are working with. Here are a few scenarios where such concepts might be relevant:

  1. Web Development (Frontend Frameworks): If you are working with a frontend framework like React, Angular, or Vue.js, you might be dealing with component schemas or metadata definitions. In this case, the ability to use choices from a meta-object definition in a section schema would depend on the specific tools or libraries you are using.

  2. Data Modeling (Database Schema Definition): If you are referring to a backend scenario where you are defining database schemas using a tool like Django ORM, SQLAlchemy, or similar frameworks, the concept of using choices from a meta-object definition in a section schema might be relevant to how you define fields and constraints.

  3. API Development (OpenAPI, GraphQL): In the context of API development, you might be working with OpenAPI specifications or GraphQL schemas. Choices and constraints might be defined in meta-objects and used in section schemas or types.