Metafields not showing on product page in Dawn Theme

Hi everyone,

I’m having an issue with metafields on my product pages. I created a metafield in the product template, but when I add a new product to my webshop, I can’t link anything to it. Even when I manually enter something (for example, the material), it does not appear on the product page.

I’m using the Dawn theme.

Someone compared their theme setup with mine and noticed that a piece of code is missing in my theme files. The metafield for the collection works correctly, but on the product page it does not.

This is the missing code:

“collapsible_content_zAgDmj”: { “type”: “collapsible-content”, “blocks”: { “collapsible_row_DkcM6T”: { “type”: “collapsible_row”, “settings”: { “heading”: “All benefits at a glance”, “icon”: “check_mark”, “row_content”: “{{ product.metafields.custom.usp | metafield_tag }}”, “page”: “” } } } }

Does anyone know how this could have happened and how I can fix it?
Any help or suggestions would be greatly appreciated!

Thanks in advance!

This looks like a part of the theme/template/section/block settings from the .json file.
This is expected to be different between stores/themes depending on configuration settings you’ve chosen.

So no, this is not a “missing” code.

You should share more details about your metafield and theme setting configuration related to the metafield.
Screenshots will help.

Thank you for your reply! Where can I find these settings? I don’t see any meta options in my theme settings. Please let me know!

Metafields are usually used as Dynamic sources for the fields on your page.

That piece of code you’ve shared uses product metafield custom.usp for row content setting of collapsible block content.

I would like to show the material on the productpage, but now it is empty.

Can you see this pictures? Sorry it is in Dutch..

See the manual on using dynamic sources, aka resource metafields, in the theme editor.
https://help.shopify.com/en/manual/online-store/themes/theme-structure/sections-and-blocks#metafields-and-dynamic-sources

Because your comparing SETTINGS, i.e. what configuration they chose to customize for their specific store.
If your sharing settings between stores your product information needs to be setup exactly the same configuration including metafields namespaces and keys.

If using dynamic sources you are actually pointing to the resource you think you are trying to use and not like a different metafield, metaobject that has a similar name or sub property.

Not all metafields are compatible with all input types.
This can be an issue here.

1 Like