---
schema_version: "1"
id: 62069e1d022a019274b30eed78e2ccc03b803fc639f28602647bd0635932ee8f
title: Supported Special Characters in Metadata Component Names
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_component_names_special_characters.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_component_names_special_characters.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a0ced6de45f3657c1e7c883f0b9bc404e084dd8088a4397831056d2898554c41
description: When naming metadata components, DevOps Center and its underlying technologies, such as Metadata API and Salesforce CLI, support a subset of special characters. To avoid issues when deploying or promoting metadata to a pipeline stage, we strongly suggest using only supported special characters in your component names.
products:
  - Salesforce Platform
release: "264"
---
# Supported Special Characters in Metadata Component Names

When naming metadata components, DevOps Center and its underlying technologies, such as Metadata API and Salesforce CLI, support a subset of special characters. To avoid issues when deploying or promoting metadata to a pipeline stage, we strongly suggest using only supported special characters in your component names.

The supported special characters are:

```
/\^$#+?()|[]{}!@$&:’,”
```

If you get the deployment error, `The deployment of work items into the next stage failed`, where the explanatory text says that the component was not found in the zipped directory, see [Error: Deployment of the work items into the next stage failed](https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshooting_special_characters_component_names.htm&release=264.0.0&type=5 "This error occurs when deploying or promoting metadata components with unsupported special characters to a pipeline stage. The error text displays the component name and indicates that it wasn’t able to find the component in the zipped directory. To fix this error, replace the non-supported special characters with their URL-encoded versions.") for details on how to fix it.