Support for bulk update of metafields?

[jagthedrummer]

The main API docs indicate that it's possible to set multiple metafields on a product with a single API call by including them as part of a product update. Is there anyway to do this through the ruby API?

https://help.shopify.com/api/reference/product#update

[wakproductions]

Not working for me either...

[wakproductions]

I've got a product like this:

v = ShopifyAPI::Variant.find(7760165896236)
v.metafield=[{namespace: 'product', key: 'product_id', value: '12345xyz', value_type: 'string'}]
v.save
#=> true

v = ShopifyAPI::Variant.find(7760165896236)

### v does not contain the metafield

[travishaynes]

@wakproductions Does this still happen if you fix the typo you have for v.metafield? It should be plural: v.metafields. If that doesn't work, I would try using a ShopifyAPI::Metafield instance in the array instead of a Hash.

[jagthedrummer]

Fixing the typo and using the ShopifyAPI::Metafield class doesn't work either.

2.4.1 :010 > shopify_shop.metafields = [
  ShopifyAPI::Metafield.new({ namespace: 'my-app', value: 'hi', key: 'hello', value_type: 'string'})
]
 => [#<ShopifyAPI::Metafield:0x007fd91a3b9bb0 @attributes={...}, @prefix_options={}, @persisted=false>] 
2.4.1 :011 > shopify_shop.save
ActiveResource::ClientError: Failed.  Response code = 406.  Response message = Not Acceptable.
	from (irb):11

[wakproductions]

@travishaynes I made the correction you suggested and it now seems to work. Thanks!

@jagthedrummer I don't think you need to enclose it in a ShopifyAPI::Metafield.new... just make it the hash: shopify_shop.metafields = [{ namespace: 'my-app', value: 'hi', key: 'hello', value_type: 'string'}]

[onedanshow]

You can also bulk add metafields this way:

product = ShopifyAPI::Product.find(12341234)
product.update_attributes(metafields: [{ namespace: 'test', key: 'test', value: 1, value_type: 'integer' }])

Updating / overriding does not work this way, though.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. It will be closed if no further action occurs in 14 days.

[github-actions]

We are closing this issue because it has been inactive for a few months.
This probably means that it is not reproducible or it has been fixed in a newer version.
If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.

If you still encounter this issue with the latest stable version, please reopen using the issue template. You can also contribute directly by submitting a pull request– see the CONTRIBUTING.md file for guidelines

Thank you!