Using Existing Customer Metafield
Froonze
Last Update setahun yang lalu
Changing both the namespace and the key of a custom field usually have or should have the purpose of using an already created customer metafield definition that probably already collected information from some customers before, for example a metafield created by another app, instead of just starting to collect information with a new one.
When you use this setting you need to take into account that this new field will give customers the option to edit personal information, contained in the metafield, that perhaps was collected before and thus will be overwritten once the customer submits it again.
When you manually enter both key and namespace, our app will check if all key, namespace and type match the ones of an existing metafield, and if they do it will create a custom field that will use the existing metafield to store the information, meaning that:
- You’ll be able to use this custom field (associated with an existing metafield) in your forms
- All already collected values will still be stored in the existing metafield
- But each customer will also be able to resubmit this information using the form and change it
To create a Custom Field and associate it with an existing metafield you can first check its namespace, key and type values in the Shopify Admin (Settings>Metafields>Customers>Definitions), then enter the same values in our settings (see pictures below). The customer metafield should be defined in Shopify (assigned to a type) and it's only possible to associate metafields of a type that we support: single line text, multi line text, decimal number, integer number, boolean, date, multi-choice. If you need to define undefined metafields in order to associate them with our custom fields, make sure that you do it following instructions given by the app that created the metafield in first instance.
Apart from the considerations above we also wouldn't recommend you having two different apps acting on the same metafield at the same time as this could cause problems of synchronization on that other app, or at least we'd advise you to consult this with them first.
