Metafields not appearing as dynamic data source

[clairegll]

Hey there, 

As you ask me @LitExtension I post my question here : )

I've created some variant metafields:

 

These metafields have data but when i want to select them on my customize, I haven't access to them ... 

 How can I do please ? 

Thanks for helping ! 

PS : I'm using Dawn theme !

[MetafieldsGuru]

Hi @clairegll ,

Sadly, it's not possible to use the variant metafields as a dynamic data source. However, you can do that with a minor theme customization. Here's the link to a related thread. Hope this helps!

[LitExtension]

Hi @clairegll,

Can you send me more detail in 2nd screenshot, its not clear so i can check it

[clairegll]

Yes of course, here I wanted to add some metafields 

and they aren't suggest as a dynamic source, I don't understand why  ...

 

whereas I created (cf screen 1). So what are the goal of metafields ?

 

[LitExtension]

Hi @clairegll,

Are you on Customize of product page? Product metafields only work on product pages.

Hope it helps!

[Unohgx]

I have a similar problem. I've created a metafield to use in the theme, but I don't find it appearing in the Product Page template editing screen.

[LitExtension]

Hi @Unohgx,

You can create a question on the community and send me the link. I will check it.
Because this will help build a better community.
Thank you.

[Createsome]

No Idea if this is still something you are looking for, but we've foung the solution for it:

Apparantly the field you want to use a metafield in has the inpu ttype "text" - which only supports single line metafields created in the Metafields Backend. Your metafields are all multi line metafields, so they are not available to select. Either you change your metafields into single line (which means you have to delete them and then create new ones) or you change the field type in the schema. To use a multiline metafield the type has to be "richtext" (Richtext is able to use multiline metafields).

If you need help setting this up feel free to comment or contact us 🙂 

Hope this solves the issue.