Metafield imports respect your definitions over column header types

When a column header and your metafield definition disagree on the type, the import used to skip the field. Now it goes with the definition and brings the value in.

🐛 Fixes

#

• Metafield types - When a column header specifies a type (like [string]) that differs from your store’s metafield definition, Altera now imports using the definition’s type instead of rejecting the value. Previously the mismatched metafield was skipped.
• Google Shopping metafields - Re-importing an export of mm-google-shopping fields, which Shopify stores with the legacy string type, now updates cleanly against the modern single_line_text_field definitions (see the Google Shopping metafields guide).