Trying to create a metafield definition for a namespace/key after metafields already exist

[jne]

I'm trying to create a metafield definition on PRODUCT owner type using GraphQL API, but there are existing metafield values for the namespace/key I'm using.

When I use metafieldDefinitionCreate, I end up with the error "Namespace and key is already in use for a set of your metafields".

I know it can be done in the Shopify Admin UI by picking "Metafields without a definition" and then adding one, but is there any way to do it with the API?

[M-Gamal]

Same Problem Here,

I can't understand why it is forbidden through the API but Permitted through the Admin Dashboard.
It should have the same behavior through both channels.

Could someone from Shopify Stuff inlight us with the purpose of the different behavior?

[SterlingHirsh]

I'm also having this problem. I have seen there's a forceCreate option that gets passed in the admin web UI, but it doesn't accept it from GraphQL.

[Vlad_BWT]

Hello!

Also have the same problem with metafieldDefinitionCreate mutation in Admin GraphQL API.

[dgtlmonk]

Any update on this ?

[CharlyTalavera]

Is there any update about this?

We need a solution so if there are Metafields created, be able to create Metafield Definitions on top of that anyway. Otherwise we have existing Metafields on some shops that we can't reuse and display on the UI.

[murphy-anker]

Any update on this

[BCSE]

Hi,

Yes, we have the same problem here.

[PlusApps]

Any update? Shopify is getting painful for the dev day by day..

[CharlyTalavera]

Hi everyone!

This week we retried this behavior, and looks like now it's working as expected.

So, if you have metafields with some namespace/key, you can create a Metafield Definition afterward without any issue.

I hope this behavior now works as everyone expected. 💫