Metadata sources for Transform Message
Where Transform Message gets its input and output structures (DataSense from connectors, Metadata Editor types from samples, schemas or the built-in editor, and preview-only sample data), and where metadata should and should not be declared.
Select and use the available sources of metadata in the Transform Message component.
~7 min read · 5 practice questions
What the exam expects
- Select the right metadata source for a Transform Message mapping: DataSense from a connector, a Metadata Editor type, or sample data.
- Keep DataSense working when a connector query is dynamic.
- Know which formats a Metadata Editor type can be built from a sample, a schema or the built-in editor.
- Declare metadata where it belongs (flow and subflow contracts) and not where it masks real types (Transform Message output).
- Shape input metadata with Set Metadata, including a list of a single-record structure.
DataSense: the Studio feature that acquires Mule event metadata automatically while you design. Metadata Editor: the Studio editor that defines payload, attribute and variable metadata. Metadata type: a named structure built from a sample, a schema or an editor. Sample data: input values typed into a Transform Message to drive its preview (DataSense, Metadata Editor).
Sources for this section (2)
Key facts
- Detail
- Connectors, schemas and sample data
- Detail
- Working connection to the connector's resource
- Detail
- Use
defaultin the interpolation so design time can resolve it
- Detail
- Preview of that component only; not propagated, not a runtime default
- Detail
- Schema only / built-in editor only
- Detail
- Defaults to
application/javawith a warning
- Detail
- Do not declare it; it masks the script's real type
- Detail
- Must declare their metadata contract
- Detail
- Turns a structure into a list of its instances
- Detail
- Operations and sources only
Sources for this section (7)
- Transform Messagedocs.mulesoft.com (opens in a new tab)
- DataSensedocs.mulesoft.com (opens in a new tab)
- Selectdocs.mulesoft.com (opens in a new tab)
- Previewdocs.mulesoft.com (opens in a new tab)
- Metadata classdocs.mulesoft.com (opens in a new tab)
- Metadata Editordocs.mulesoft.com (opens in a new tab)
- DataSense Supportdocs.mulesoft.com (opens in a new tab)
- When a Transform Message writes both the payload and a variable, which output does the Preview pane show?
- Which Transform Message editor mode shows only the input structure beside the code?
- Why can dynamic metadata for an operation's attributes be left out?
- When you want every new Transform Message to open in a particular editor mode, where do you set it?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (5 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both