-
Notifications
You must be signed in to change notification settings - Fork 1
Metadata Type Support
Jörn Berkefeld edited this page Mar 30, 2023
·
4 revisions
The mcdev-copado extension supports a subset of what mcdev supports at any given time. Some metadata types are either in a beta state or do not support templating and hence are not supported by this extension yet.
The following metadata types are currently supported:
| MetadataType | Supported by Copado | Description |
|---|---|---|
| Asset (Content Builder) | Yes | Assets from Content Builder grouped into subtypes. |
| Automation | Yes | Used via Automation Studio directly - or indirectly via Journey Builder & MC Connect. |
| Automation: Data Extract Activity | Yes | Creates zipped files in your FTP directory or convert XML into CSV. |
| Automation: File Transfer Activity | Yes | Unzip, decrypt a file or move a file from secure location into FTP directory. |
| Automation: Filter Activity | in backlog | Part of how filtered Data Extensions are created. Depends on type "FilterDefinitions". |
| Automation: Import File Activity | Yes | Reads files in FTP directory for further processing. |
| Automation: SQL Query Activity | Yes | Select & transform data using SQL. |
| Automation: Script Activity | Yes | Execute more complex tasks via SSJS or AMPScript. |
| Campaign Tag | in backlog | Way of tagging/categorizing emails, journeys, and alike. |
| Content Area (Classic) | - |
DEPRECATED: Old way of saving Content Blocks; please migrate these to new Content Blocks (Asset: ...). |
| Data Designer Attribute Groups | in backlog | Groupings of Set Definitions (Data Extensions) in Data Designer. |
| Data Designer Set Definitions | in backlog | Data Extensions linked to Attribute Groups in Data Designer. |
| Data Extension | Yes | Database table schemas. |
| Data Extension Template | - | OOTB Database table schemas used for special cases like Transactional Journeys. |
| Data Extract Type | - | Types of Data Extracts enabled for a specific business unit. This normally should not be stored. |
| E-Mail (Classic) | - |
DEPRECATED: Old way of saving E-Mails; please migrate these to the new E-Mail (Asset: message). |
| E-Mail Send Definition | in testing | Mainly used in Automations as "Send Email Activity". |
| FileLocation | - | A File Location that can be used for the export or import of files to/from Marketing Cloud. |
| Folder | Yes | Used to structure all kinds of other metadata. |
| Journey | in testing | Journey from Builder (internally called "Interaction"). |
| Journey: Entry Event Definition | in testing | Used in Journeys (Interactions) to define Entry Events. |
| List | - | Old way of storing data. Still used for central Email Subscriber DB. |
| Mobile Connect Code | - | Mobile Connect Shore or Long Codes used for sending. |
| Mobile Connect Keyword | in testing | Mobile Connect keywords configured within the Business Unit. |
| Role | Yes | User Roles define groups that grant users access to SFMC systems. |
| Transactional Email | Yes | Lets you send immediate Email messages via API events |
| Transactional Push | Yes | Lets you send immediate Push messages via API events |
| Transactional SMS | Yes | Lets you send immediate SMS messages via API events |
| Triggered Send | Yes | DEPRECATED: Sends emails via API or DataExtension Event. |
| User | - | Users and Installed Packages, including their assigned Roles, BUs and personal permissions |
Copyright (c) 2022-2023 Accenture. MIT licensed. Main contributors: Jörn Berkefeld