Jesse_Vogt
Shopify Staff
Contact Me
Status
Offline
Last Activity
‎03-24-2023 03:36 AM
Topic Started
0
Topics Started
Topic Solutions
2
Solutions
Post Count
14
Posts
Post Kudos
10
Likes

Community Badges

No content to show

User Activity

@jg_va thanks for reporting this. I was able to reproduce and have flagged this inconsistency with the appropriate team so someone will be looking into this.   Until we have a fix in place the only guidance I can offer would be make a call back into ...
Hi @nayantaraSingh    I see two options:   1. Use aliases for each of the metafield ids you need back. For example: size: metafield(namespace: "custom", key: "size") { id } capacity: metafield(namespace: "custom", key: "capacity") { id } 2. Pick the ...
The issue with metafieldDefinitionCreate should now be resolved.
Hi all,   Jesse from the Metafields team here. Thanks for bringing this to our attention. This was an error on our side and the fix will be shipping today. I will follow up here when it is live.    
@zstanford @bpthanh87 fix just went out and I verified that the value is updating correctly on my own store. 
Hi @zstanford,   Jesse here from the Metafields team. Thanks for reporting this - I was able to reproduce this and will work with the team to figure out what is going on.   Jesse
Hi @kamon000, Jesse here from the Metafields team.   The description in your screen shot is the description on the definition. The description you are asking for in your graphql query is for the description on the metafield. As far as I know, the the...
Hi @Jean_Baptiste1 ,   Just to follow up on what @LitCommerce said. The Metafields team is shipping the ability to edit definition options by the end of the year which should make this process much easier.
Hi @epetroel, Jesse from the Metafields team here. The only way I am able to reproduce your issue is if I leave off the trailing ".json" - could you double check that you are attempting to POST to "/2021-10/pages/PAGE_ID/metafields.json"? Also double...
Hi @MattiaM , Jesse here from the Metafields team.  You are correct that translations for Metafields do come back as a string. As you have observed once it becomes a string you are not able to index into it as you would expect. I have created an issu...
We do not offer a way to query all namespaces outside of paging through all metafields and collecting the namespaces yourself. If you can share, what is your use case for this?
We do not expose this in the API directly but if you are using graphql unstable, the Metafield node returned by the metafields connection does have a nullable definition field. If you are able to share, what is your use case for getting metafields wi...
Thanks for letting us know about this and I verified that this is an issue. The intention is that type can be used as a query parameter in a smilier fashion to how value_type was being used. I am writing up an issue to track this bug and can respond ...
Thanks for letting us know about this and I verified that this is an issue. While a fix is being worked on you should be able to use `valueType: STRING`. In 2021-07 it is deprecated but should still be available.
This widget could not be displayed.
This widget could not be displayed.