Hi everyone,
I’m trying to query products by metafield value and collection id using GraphQL API but it seems doesn’t work.
The screenshot below is showing that the first product from target collection has valid metafield value.
Do you guy have any idea?
Thanks a lot
You can’t filter by metafields, that’s a limitation.
However you could query all products of a collection and get their metafields:
query ($collectionId: ID!, $first: Int!) { collection(id: $collectionId) { products(first: $first) { edges { node { id title metafield(namespace: “custom”, key: “your_key”) { value } } } pageInfo { hasNextPage endCursor } } } }
This is incorrect, you can query using metafields:
Totally agree with you. I’ve tried to filter by collection_id and metafield separately. It’s working correctly. But when I combine both, it doesn’t work anymore
Hi @jenhacool,
I can confirm that you are filtering this query correctly, and this should work.
This is actually a known issue that our developers are currently aware of, specifically with the collection_id fitler not working when combined with certain other filters such as the metafield filter.
I’ve reached out to our developers internally to help look into this further and we will keep you updated here as soon as we have any more information to share. Though in the meantime, I know it’s not ideal, but I may recommend filtering the products query with the metafield fitler, and using the inCollection field on the product object to see if the returned products are in the collection you’re trying to filter for or not.
I also encountered a similar bug with product queries.
Inaccurate results occur when complex conditions are combined.
In the end, I worked around the issue by using multiple queries.
Thanks a lot for you reply. That solution doesn’t work in our case because we need to implement pagination. Do you guy have any other solutions
From the screenshots, the combined query looks like it’s targeting a different metafield than the one you proved exists. In screenshot 1 you read sapo.optimizationSite, but in screenshot 2 you filter on $app.optimizeState. Since products(query: ...) does support combining collection_id with metafield filters, I would first double-check the exact namespace/key and whether that metafield definition is filterable.
Hi @jenhacool,
I do understand it’s not ideal, especially if you’re needing to paginate over a large amount of results, though it’s not impossible with the workaround, you’d just need to paginate through all of the results filtered by metafield, then cache the results on your end and parse through them, removing any results that have inCollection: false.
Alternatively, you can use Bulk Operation Queries to request ALL results at once, and not have to paginate through the results, though this is an asynchronous operation, and you’ll still need to parse the results after, removing any results that have inCollection: false
