Metadata API Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
ManagedContentType
File Suffix and Directory Location
ManagedContentType components have the suffix managedContentType and are stored in the managedContentTypes folder.
Version
ManagedContentType components are available in API version 47.0 and later.
Special Access Rules
ManagedContentType is only available if Salesforce CMS and digital experiences are enabled for your org.
Fields
| Field Name | Field Type | Description |
|---|---|---|
| description | string | Describes the custom content type defined in this ManagedContentType declaration. |
| developerName | string | Required. Unique name for the custom content type. For example: OurSpecialContent_c |
| isMetadataContent | boolean | When true, any content created from this content type is converted to metadata. Default value is false. Availabe in API version 63.0 and later. |
| managedContentNodeTypes | ManagedContentNodeType[] | Nodes included as part of this custom content type. When rendered as a form in the Digital Experiences app, each node is represented as an individual field. |
| masterLabel | string | Required. Declares the name of the content type as it appears in the UI. |
ManagedContentNodeType
Represents the structure of individual nodes within the custom content type.
Declarative Metadata Sample Definition
The following is an example of a ManagedContentType component.
<?xml version="1.0" encoding="UTF-8"?>
<ManagedContentType xmlns="http://soap.sforce.com/2006/04/metadata">
<developerName>myContentType</developerName>
<masterLabel>My Content Type</masterLabel>
<description>This is the description for my content type</description>
<managedContentNodeTypes>
<nodeName>title</nodeName>
<nodeLabel>Content Title</nodeLabel>
<nodeType>NAMEFIELD</nodeType>
<placeholderText>Placeholder Text for title</placeholderText>
<helpText>Help Text for title</helpText>
<isLocalizable>true</isLocalizable>
<isRequired>true</isRequired>
</managedContentNodeTypes>
<managedContentNodeTypes>
<nodeName>textnode</nodeName>
<nodeLabel>Content Text</nodeLabel>
<nodeType>TEXT</nodeType>
<placeholderText>Placeholder Text for Content Text</placeholderText>
<helpText>Help Text for Content Text</helpText>
<isLocalizable>true</isLocalizable>
<isRequired>false</isRequired>
</managedContentNodeTypes>
<managedContentNodeTypes>
<nodeName>richtextnode</nodeName>
<nodeLabel>Content RichText</nodeLabel>
<nodeType>RTE</nodeType>
</managedContentNodeTypes>
<managedContentNodeTypes>
<nodeName>multilinetextnode</nodeName>
<nodeLabel>Content MultilineText</nodeLabel>
<nodeType>MTEXT</nodeType>
</managedContentNodeTypes>
<managedContentNodeTypes>
<nodeName>imagenode</nodeName>
<nodeLabel>Content Image</nodeLabel>
<nodeType>IMG</nodeType>
</managedContentNodeTypes>
</ManagedContentType>Usage
For each custom content type you create, there must also be a CMS Content page created in any Experience Cloud site that displays the content. Each Content page serves as the detail page for all content of a single content type. See Create Custom Pages with Experience Builder.
Wildcard Support in the Manifest File
This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.