---
schema_version: "1"
id: c46fe0e79d7e402e8ed641583b0668f8bc049b99c85e21b37440b420129cb5e0
title: Preview the Output of a Transformation (Anypoint Studio)
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/transform-preview-transformation-output-studio-task.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/transform-preview-transformation-output-studio-task
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7830082090d4de5cded4100005985184e55b73b16d92aad7ba2746545264bb13
description: MuleSoft Documentation Site
release: "4.3"
latest: false
---
---
product: Mule Runtime
version: 4.3
---

# Preview the Output of a Transformation (Anypoint Studio)

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

You can provide sample input data to your Transform Message component to see how the transformation
affects it. You don’t need to deploy your project to use this feature. A sample output is updated in
real time as you make changes both to the sample input and the transformation.

1.  Click on the root of the input pane and select **Edit Sample Data**.

    ![sample data](/mulesoft/current/en-us/mule-runtime/4.3/_images/dataweave-edit-sample-data.png)

    A new tab opens with an empty scaffolding of your input structure. Values are populated with the
    string `????` as a placeholder.

    > [!NOTE] When the input is of type POJO, samples must be written in DataWeave format. This is
    > not a transformation in itself, just a way to express how data is structured.

2.  Replace placeholder values with sample values to see how they are mapped out to the preview
    pane.

    ![sample data](/mulesoft/current/en-us/mule-runtime/4.3/_images/dw-populate-sample-data.png)

    > [!TIP] To reset the sample to the original scaffolding with placeholders, click the
    > **rescaffold button** ![rescaffold](/mulesoft/current/en-us/mule-runtime/4.3/_images/dw-rescaffold-button.png). Note that any sample
    > data you provided is lost.

3.  Enable the preview pane by clicking on the **Preview** button on the top-right of the editor.

    As you make changes in the DataWeave code or your sample data, notice how the output data
    structure changes.

    > [!NOTE] If your transformer has multiple outputs (for example, to both the payload and a
    > variable), the **Preview** pane displays the one corresponding to the currently selected
    > transformation.

4.  Test your transformation for any special characters or structures that might arrive, verify that
    the output is what you expected.

    > [!NOTE] Note that samples defined in this pane work only within the **Transform Message**
    > component, they don’t alter the metadata that’s propagated to other components in the flow,
    > and their values aren’t propagated onwards. They aren’t used in your running application as
    > default values nor in any other way.

## See Also

[Workflow: Create a Mapping](https://docs.mulesoft.com/mule-runtime/4.3/transform-workflow-create-mapping-ui-studio)

[Transform Message Component](https://docs.mulesoft.com/mule-runtime/4.3/transform-component-about)

[DataWeave Language](https://docs.mulesoft.com/mule-runtime/4.3/dataweave)