Hello, if I create private metafields with reserved prefixes can I request them with the query privateMetafields ?
I only want to get metafields, I don’t want to get the resource.
Topic summary
Main issue: Whether metafields created with reserved prefixes can be fetched via the GraphQL privateMetafields query without fetching the parent resource.
Key clarification:
- “Private metafields” (a distinct Shopify entity) are different from regular metafields that simply use a reserved prefix (app-private by convention).
- The privateMetafields query applies only to the dedicated Private Metafield entity, not to regular metafields with reserved prefixes.
What to use instead:
- For regular metafields that use a reserved prefix, query them as standard metafields (e.g., by ID) using the metafield query in Admin GraphQL.
Outcome: The question is resolved. Use privateMetafields only for true Private Metafields; use the metafield query for reserved-prefix regular metafields. Links to official docs were provided for both concepts.
Hi there, private metafields as documented here are a different kind of entity from regular metafields that use a reserved prefix (and are therefore private to the owning app). If you are using the latter, then you can’t query them with privateMetafields, they are regular metafields and you can query them by id with the metafield query.