How to change a key or namespace of existing metafield

Modified on Sat, 11 May 2024 at 07:04 PM



This option allows you to change the namespace, key, or both at the same time for a specified metafield. Can be applied to all resources and/or a filtered selection.

In case you are not familiar with the basics of our bulk editor, you should check out this step-by-step tutorial before you proceed.

Configuring a bulk action

Select the "Change namespace or key" option in the drop-down menu:

Next, you can specify the details for a metafield to be updated. Press the Select metafield button (1) to reveal the available options (2). Select the one that fits your specific task the most:

Specifying the metafield data

Regardless of what attribute you are about to change, both the namespace and key must be specified for the "old" and "new" versions. Let's use a real-world example to make it easier to understand. Say, there is a metafield assigned to 500 products with the following settings: 

1) namespace set to "shipping_info";

2) key set to "weight";

If we were to change its key only and keep the namespace unaffected, the editor must be configured like this:

If we were about to change the namespace only and keep the key, it would look like this:

If we were about to change both, then it would look like this:

Removing original (old) metafields

In some cases, you might want to keep the original/old versions of metafields along with the new ones. However, if you don't need the old data and want it to be removed, you can do that with the very same bulk action. All you need to do is enable the respective option:

Running multiple bulk edits

You can configure up to 3 concurrent bulk edits. If you want to update more metafields, press the Add new action button and repeat the process:

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article