Metafield definition and access settings, this is a big problem

[Next_Cart]

We are migrating products from our client's online store to Shopify using the latest API version 2023-10. The product attributes are migrated as metafields, and we just noticed a serious problem with metafield definition and access settings since the API version 2023-01 to 2023-10.

There are some issues/limitations:

• The namespace is required to be the app reserved namespaces. You cannot create a metafield definition in a custom namespace without the app reserved prefix, this is the error: "Setting access controls on a definition under this namespace is not permitted".
• The store owner cannot change the metafield definitions once they are imported. You can only delete the metafield definitions through the app you used to import them, but this will not work with custom apps.
• The access "MERCHANT_READ_WRITE" is the only setting you can use if you want to be able to view and edit the metafields via admin. This leads to a problem: one year later, if the store owner wants to use another app to interact with the metafields, or copy data to another store, you'll need to go back and grant access to that app. But, this becomes impossible if the metafield definitions were imported via a custom app and that custom app was removed for some reason.

Shopify developers, e-merchants, web agencies and developers should take note of thess issues. I hope you will find out a comprehensive solution.

[JohnBerry · Accepted solution]

Hello,

You should be able to create a metafield definition in a non app reserved namespace (e.g. "custom") as long as you are not setting a value for the access input. If you do not use a reserved namespace, the merchant and other apps should be able to edit the definition and set metafield values.

[homerjam]

How should I go about creating a definition in a "custom" namespace with storefront access??

EDIT/UPDATE:

So it seems that creating the namespace with "$app:custom" is the answer

[JohnBerry]

That is correct. Prefixing a namespace with "$app:" produces a metafield definition in a reserved namespace that is owned by the app that created it. The owning app has full control over the definition including the definition's admin and storefront access settings.

Apps can also create non-reserved namespace metafields (e.g. "custom") but cannot set storefront or admin access. In the 2024-01 API release and beyond, storefront access for non-reserved namespace metafields can only be set from within the Admin.

[m4rc]

@JohnBerry 

Do you know we will be able to create non-reserved namespace metafields for any owner type?

I would like to create a shop metafield as a non-reserved namespace metafields, but it seems like there's no way to currently define it from the Shopify Admin.

[JohnBerry]

Shop metafields can be created using the metafieldDefinitionCreate Admin API mutation with an ownerType = SHOP.

Shop metafields cannot be created through the Admin interface.

[sebizox]

Within an app, I attempted to create a metafield definition with the following settings:

metafieldDefinitionCreate(definition: {

  name: "Custom Test",

  namespace: "customtest",

  key: "config",

  type: "json",

  ownerType: SHOP

  access: {

    admin: MERCHANT_READ_WRITE

    storefront: PUBLIC_READ

  }

}) {

  createdDefinition {

    id

  }

}

I launch shopify's graphiql app and can successfully fetch the metafield value using the admin API endpoint. When I switch it to Storefront, i get a null value instead. Does this not work on metafields where the SHOP is the ownerType? When I set a metafield value, i used the shopid for the `ownerId`, but we're still having issues accessing this via Storefront.

We were deploying our app to another store within our plus plan to attempt to set up a staging site, but we're unable to deploy due to this inconvenience. We're assuming the metafield we have on the SHOP owner type is grandfathered in or added a long time ago before the metafield storefront visibility mutation was deprecated. Any insights you can provide?

I must also mention, that we tried without the `access` input, and we yield the same result.

[newbie_01]

Hi. Is there a way to access a product image metafield from the storefront api and liquid?

I defined it with [storefront] => PUBLIC_READ access, but I can't find any query to access it.  

The image object in the back end include metafields, but not the one in the front end.

Thanks

[Next_Cart]

A non app reserved namespace with no access input is the best solution 👍.

*Note: if anyone is trying this solution, remember to use the API stable versions, as it doesn't work with the "Unstable" versions.

Thank you so much, John!

[Teetoy]

hello