Shopify app grapql metafieldsSet update notice for app own metafiled

Shopify Apps
,
1

9 MONTHS LEFT UPDATE DEADLINE: OCT 1, 2023 Update to version 2023-01 or later API CHANGE ENDPOINT LAST DETECTED (UTC)As of 2023-01, metafieldsSet no longer requires type when a corresponding metafield definition exists. View change belove code example in my app

query: `mutation CreateAppOwnedMetafield($metafieldsSetInput: [MetafieldsSetInput!]!) {
        metafieldsSet(metafields: $metafieldsSetInput) {
          metafields {
            id
            namespace
            key
          }
          userErrors {
            field
            message
          }
        }
      }`,

      variables: {
        metafieldsSetInput: [
          {
            namespace: "secret_keys",
            key: "myapps",
            type: "single_line_text_field",
            value: "App Settings",
            ownerId: my_app_install_id.body.data.appInstallation.id,
          }
]
}
2

Were you able to find a fix for this issue ?

3

@hitanshu88 no

4

@1080
I found out the solution. Use the below request →
query →

mutation MetafieldsSet($metafields: [MetafieldsSetInput!]!) {
metafieldsSet(metafields: $metafields) {
metafields {
key
namespace
value
}
userErrors {
field
message
code
}
}
}

variables →

{
“metafields”: [
{
“namespace”: “namespace”,
“key”: “key”,
“type”: “type”,
“value”: “value”,
“ownerId”: “ownerId”
}
]
}

5

@hitanshu88 This was I am using but it was Still showing the API notice into the partner portal.
I also flow the the as per dev doc. Still Notice showing. do you see any still API notice ?

6

@1080 i am not able to c the notice any longer

7

@hitanshu88 yes notice will gone out, but i did not change any things then why that time showing this notice any idea ?

Thanks for the your answer.

8

Hello @hitanshu88

I am also facing the same issue

Are we sure that this will solve the problem. Because I see that the Warning in itself is “metafieldsSet no longer requires type when a corresponding metafield definition exists”. But I see that we are using the API with type parameter.

Also do we need to create any definitions for the metafields separately before actually upadting the metafield using this API?