Accentuate Custom Fields
  • Welcome!
  • Introduction
    • Getting started with ACF
    • Field scopes
    • How to show fields in your storefront
  • Dashboard
    • Reference Manager
      • Creating a new reference within Reference Manager
    • Filter & Group
      • Filter editor
      • Filter usage
    • Activity log
    • App settings
  • Field Definitions
    • Fields & Sections
    • Deciding on a field type
    • ACF Field types
      • Text
      • Markdown text
      • HTML
      • Checkbox
      • Selection
      • Tags
      • Number
      • Date
      • Color
      • Media v1 (legacy)
      • Media v2
      • Custom Object (JSON)
      • Multi-language Text
      • Reference fields
      • References to Global fields
    • Shopify Field types
      • Shopify » Single line text
      • Shopify » Multi-line text
      • Shopify » Boolean
      • Shopify » Color
      • Shopify » Custom objects (JSON)
      • Shopify » URL
      • Shopify » Date
      • Shopify » Date and Time
      • Shopify » Integer
      • Shopify » Decimal
      • Shopify » Weight
      • Shopify » Volume
      • Shopify » Dimensions
      • Shopify » Reference fields
    • Automatic tagging
    • Large sets
    • Field contexts
    • Field context filters
    • Copy and paste fields
    • Change field name and type
    • Import existing fields
    • Linking multiple stores
  • The Editor
    • Using the editor
    • Promote fields to sidebar
    • Layouts
    • Hide from search
    • Repeatable fields
    • Version control
    • Update value on order creation
  • Bulk Import & Export
    • Export custom field values
    • Import custom field values
    • Metaobject export / import
  • METAOBJECTS
    • What are Metaobjects?
    • Metaobject Definitions
    • Metaobject instances / values
    • Displaying Metaobjects on your storefront
    • Metaobject export / import
  • THEME EXTENSIONS
    • SEO keywords
    • Sticky promo bar
    • Products promotion
  • Liquid Guides
    • Learning Liquid
    • Resize & crop images
    • Check for empty values
    • Access field definitions
    • Order notifications
    • Allow customers to change their field values
  • OTHER
    • Webhooks
    • API
      • Access to custom fields
      • Endpoints
  • Help
    • FAQ
      • Why are one of my products no longer showing in my reference field?
      • I have multiple products/variants with the same name
      • How do I make changes to my field values in bulk?
      • I added a new field definition but it is not showing in my storefront
      • How do I copy my field setup to another store?
      • My fields are still showing after I have deleted their field definition
      • Why are none of my fields showing in the editor?
      • My newly created object in Shopify is not available in ACF
      • Reference lists are empty?
      • Why am I seeing a "value cannot exceed 100,000 characters" error when saving?
      • Why can't I name my field "first", "last" or "size"?
    • Need help?
  • Product
    • Changelog
    • Feedback & Suggestions
Powered by GitBook
On this page
  1. Field Definitions

Change field name and type

PreviousCopy and paste fieldsNextImport existing fields

Last updated 10 months ago

This article serves to communicate the risks involved in changing a field's name, namespace and/or data type. It's important to note that ACF won't stop you from carrying out the changes, since the rationale for doing it can vary greatly. Normally, ACF will show these field properties as read-only for already created fields, but it's possible to edit these fields by clicking the small "lock" icon in the lower-left corner of the dialog:

The reason behind making this just a tiny bit difficult is that changing an existing field's definition of name and/or namespace may cause loss of access to any already defined values for that particular scope that use the current name and namespace combination.

Or, maybe worse, you may point your new name/namespace combination to some already defined fields (by other apps, maybe) with incompatible values.

Changing a field's data type may cause undesired effects, if the field's existing data is not compatible with the new type and may require changes to your theme. Please only change a field's type when you know what you are doing and always consult the below table for any issues that may arise. This may not be an exhaustive list of issues that may arise from changing a field's type, so make sure you are planning a change carefully.

A change of a field's type is always possible when there are no existing values tied to the definition (no values entered for a product, a page, etc). However, when existing values are already in place, care must be taken before carrying out a change. Please see the below table for how field types can be changed. Also note that while something is possible from a technical standpoint, it doesn't mean it's a good idea. But ultimately, this is for you to decide.

Field type change overview

Text - can be changed to any of the following:

  • HTML

  • Checkbox

  • Selection

  • Tags

  • Number

  • Color

  • Multi-language Text

  • Multi-language HTML

If a Text field is changed to a Checkbox, any existing value will cause the checkbox to become checked

To change to a Multi-language field type, get in touch with support beforehand

Markdown - can be changed to:

  • JSON

Checkbox - can be changed to any of the following:

  • Text

  • HTML

  • Selection

  • Tags

If changed to a Selection, be sure to include the value "true" in the list of options

Selection - can be changed to any of the following:

  • Text

  • HTML

  • Markdown

  • Tags

  • Number

Only change to a Number if existing selections are single-selection numbers

Tags - can be changed to any of the following:

  • Text

  • HTML

  • Markdown

  • Selection

Number - can be changed to any of the following:

  • Text

  • HTML

  • Markdown

  • Selection

  • Tags

Color - can be changed to any of the following:

  • Text

  • HTML

  • Markdown

  • Selection

  • Tags

Multi-language Text - can be changed to any of the following:

  • JSON

  • Multi-language HTML

  • Multi-language Markdown

Multi-language Markdown - can be changed to:

  • JSON

Multi-language HTML - can be changed to:

  • JSON

Reference to ... - can be changed to any of the following:

  • Text

  • Tags