Hi everyone,
I’m reaching out to see if anyone else is experiencing issues with ShopifyQL via the Admin API since last week.
We have a Power Query implementation that retrieves sales data grouped by custom order metafields. This setup has been working reliably for a couple of months, but as of last week, it started throwing an error. Api version is 2026-04
The Issue: When executing a ShopifyQL query via the API, the system returns: Metafield Column Not Found: Metafield 'order.metafields.custom.origen_venta' not found
Key Observations:
-
Front-end works: If I run the exact same query within the Shopify Admin “Reports” builder, it executes perfectly and returns the data.
-
Regression: This query worked fine until roughly a week ago.
-
Scopes: We have verified that the Custom App has
read_custom_dataandread_all_ordersscopes correctly enabled.
Steps to Reproduce: We use a generic Power Query function to interface with the shopifyqlQuery endpoint:
Code snippet
(ShopifyQL_Query as text) =>
let
ApiUrl = "https://" & ParamShopName & ".myshopify.com/admin/api/" & ParamApiVersion & "/graphql.json",
Payload = Json.FromValue([query = "{ shopifyqlQuery(query: """ & ShopifyQL_Query & """) { tableData { rows } } }"]),
Source = Function.InvokeAfter(
() => Json.Document(Web.Contents(ApiUrl, [
Headers = [#"X-Shopify-Access-Token" = ParamAccessToken, #"Content-Type" = "application/json"],
Content = Payload,
ManualStatusHandling = {429}
])),
#duration(0,0,0,1)
),
Rows = if Record.HasFields(Source, "data") and Source[data][shopifyqlQuery] <> null
then Source[data][shopifyqlQuery][tableData][rows]
else {}
in
Rows
Query executed: FROM sales SHOW net_sales, orders GROUP BY day, order.metafields.custom.origen_venta SINCE 2026-01-01 UNTIL 2026-01-31 ORDER BY day ASC
I have checked that the metafield is queryable:
{
“node”: {
“key”: “origen_venta”,
“type”: {
“name”: “list.single_line_text_field”
},
“capabilities”: {
“analyticsQueryable”: {
“eligible”: true,
“enabled”: true
}
}
}
},
Question: Has there been a recent change in how the ShopifyQL API handles metafield resolution compared to the internal Report builder? Is there any additional configuration required to “expose” these metafields to the API endpoint specifically, or is this a known regression?
Any guidance or troubleshooting steps would be greatly appreciated.