I have a number of custom data metafields that do not have a definition, however when I attempt to add a definition (e.g. Single line text) to an existing metafield I get the following error when saving, which doesn’t appear to be a validation error but more a generic error:
Topic summary
Users are encountering errors when attempting to add definitions to existing custom metafields that currently lack definitions.
Error Details:
- When trying to save a metafield definition (e.g., “Single line text”), a generic error appears during the save process
- The network API call reveals a specific validation error:
"Field is not defined on MetafieldDefinitionInput"related to thecopyToOrderparameter - The error message indicates that
copyToOrderis being passed in the input but is not a valid field onMetafieldDefinitionInput
Resolution:
- One user reported that after retrying the operation, it eventually worked successfully
- The issue appears to be intermittent or may have been resolved
Screenshots of both the error message and API response were shared to illustrate the problem.
I am experiencing the same issue.
I checked the network API call and it shows the following error, screen shot also attached.
{
“errors”: [
{
“message”: “Variable $input of type MetafieldDefinitionInput! was provided invalid value for copyToOrder (Field is not defined on MetafieldDefinitionInput)”,
“locations”: [
{
“line”: 1,
“column”: 45
}
],
“extensions”: {
“value”: “{"visibleToStorefrontApi"=>false, "useAsCollectionCondition"=>false, "useAsAdminFilter"=>false, "copyToOrder"=>false, "pin"=>true, "namespace"=>"global", "key"=>"test", "type"=>"json", "validations"=>, "name"=>"Test", "description"=>"", "ownerType"=>"PRODUCT", "forceCreate"=>true}”,
“problems”: [
{
“path”: [
“copyToOrder”
],
“explanation”: “Field is not defined on MetafieldDefinitionInput”
}
]
}
}
]
}
@agiledigital I tried it again. It’s working now. Hope it works for you too.

